Repository navigation
fix: let migrate run in production without SSO settings - #12
Merged
Merged
Conversation
The pod's migrate init container has APP_ENV=production but not the SSO variables, so the production SSO requirement in Config::from_env stopped it and the API pod never started. Check it after the migrate branch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cloud API pods were stuck after #10: the
migrateinit container runs withAPP_ENV=productionbut without the SSO variables, so the new production SSO check inConfig::from_envmade it exit. The check now runs inmainafter themigratebranch.Verified locally:
knotree-api migratewithAPP_ENV=productionsucceeds; serving without SSO still fails withSSO_ENABLED=true is required in production.🤖 Generated with Claude Code