Vachan Access new release 26.05.14-beta

[shazaleen]

CodeAnt-AI Description

Release Vachan Access and AI with Kong gateway setup

What Changed

• Updated the Vachan Access and Vachan AI services to the 26.05.14-beta release
• Added Kong gateway services for staging, including initial database setup and exposed proxy/admin ports
• Set the AI service to use a fixed config path, added service limits, and enabled a service token for authenticated access
• Kept the AI worker service disabled in the compose files
• Extended Kratos session lifespan from 60 minutes to one year

Impact

✅ Staging deploys with Kong gateway support
✅ Longer login sessions
✅ Clearer AI service access control

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[codeant-ai]

🟠 Architect Review — HIGH

Kong's Postgres database is created only via the Postgres init script mounted as init-kong.sql, which runs only on first initialization of the vachan-db volume; on existing staging volumes the kong database will not be created, causing kong-migrations bootstrap to fail when Kong is introduced into an existing environment.

Suggestion: Make Kong DB/schema provisioning idempotent and upgrade-safe by adding a pre-start check or migration job that creates the kong database if missing on every deployment, rather than relying solely on the one-time Postgres initdb script.

Fix in Cursor | Fix in VSCode Claude

(Use Cmd/Ctrl + Click for best experience)

Prompt for AI Agent 🤖

This is an **Architect / Logical Review** comment left during a code review. These reviews are first-class, important findings — not optional suggestions. Do NOT dismiss this as a 'big architectural change' just because the title says architect review; most of these can be resolved with a small, localized fix once the intent is understood.

**Path:** docker/docker-compose-staging.yml
**Line:** 132:132
**Comment:**
	*HIGH: Kong's Postgres database is created only via the Postgres init script mounted as init-kong.sql, which runs only on first initialization of the vachan-db volume; on existing staging volumes the kong database will not be created, causing kong-migrations bootstrap to fail when Kong is introduced into an existing environment.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
If a suggested approach is provided above, use it as the authoritative instruction. If no explicit code suggestion is given, you MUST still draft and apply your own minimal, localized fix — do not punt back with 'no suggestion provided, review manually'. Keep the change as small as possible: add a guard clause, gate on a loading state, reorder an await, wrap in a conditional, etc. Do not refactor surrounding code or expand scope beyond the finding.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

[codeant-ai]

CodeAnt AI finished reviewing your PR.