docs(self-host): document AGENTA_SERVICES_INTERNAL_KEY - #6276
Conversation
v0.114.0 (71a2857) added AGENTA_SERVICES_INTERNAL_KEY as a required secret: the API's startup lifespan now calls validate_platform_runtime_key() unconditionally and raises if it is unset or the "replace-me" placeholder, so the API refuses to start without it. The example env files, the Helm chart, and the Railway automation scripts were already updated for this, but the public self-host docs and the EE compose README were not, so a self-hoster following only the docs would hit an undocumented startup crash. Adds the key alongside AGENTA_AUTH_KEY/AGENTA_CRYPT_KEY wherever those are documented as required secrets: the configuration reference, the Docker Compose remote-deploy guide, the Kubernetes deploy guide (values, secrets table, and troubleshooting), the Railway deploy guide, and the EE Docker Compose README.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Agenta Team seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 6 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe documentation now requires ChangesServices Internal Key
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change documents a required self-hosting secret across the relevant deployment guides; no actionable merge-blocking risk remains beyond normal documentation checks. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.) ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Organization UI (inherited)
Review profile: CHILL
Plan: Pro Plus
Run ID: 8c4dc698-c43f-4874-8ab2-c7cf8eb5b67a
📒 Files selected for processing (5)
docs/docs/self-host/deploy/01-deploy-remotely.mdxdocs/docs/self-host/deploy/03-deploy-to-kubernetes.mdxdocs/docs/self-host/deploy/04-deploy-on-railway.mdxdocs/docs/self-host/reference/01-configuration.mdxhosting/docker-compose/ee/README.md
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.
- deploy-remotely.mdx: "the two Agenta keys" -> "the three Agenta keys" now that AGENTA_SERVICES_INTERNAL_KEY is listed alongside AUTH_KEY/CRYPT_KEY. - deploy-to-kubernetes.mdx: the existing-Secret requirements list was still AGENTA_AUTH_KEY/AGENTA_CRYPT_KEY/POSTGRES_PASSWORD only. A user following that instruction would omit AGENTA_SERVICES_INTERNAL_KEY from their pre-created Secret and hit the API's startup validation failure.
Summary
AGENTA_SERVICES_INTERNAL_KEYas a required secret: the API's startuplifespan()now callsvalidate_platform_runtime_key()unconditionally and raises if the key is unset or thereplace-meplaceholder, so the API refuses to start without it.env.oss.gh.example,env.oss.dev.example,env.ee.gh.example,env.ee.dev.example), the Helm chart (secrets.yaml,values.schema.json,values.oss.example.yaml), andhosting/railway/oss/README.mdalready document it — but the public self-host docs and the EE Docker Compose README did not, so a self-hoster following only the docs would hit an undocumented startup crash on upgrade.AGENTA_AUTH_KEY/AGENTA_CRYPT_KEYare already documented as required secrets: the configuration reference, the Docker Compose remote-deploy guide, the Kubernetes deploy guide (values snippet, secrets table, troubleshooting section), the Railway deploy guide, and the EE Docker Compose README.Test plan
v0.114.0source (71a2857a2a) that this key has noAGENTA_AUTH_KEYfallback and that the API's startup validation is unconditional.docusaurus build) if CI runs it on this PR.https://claude.ai/code/session_01LDH8EkbpV3sQDj2kAww5Lh