fix: make InitAuthConfig graceful on missing IAM app#22
Merged
Conversation
… app The cloud-api was crashing on startup (CrashLoopBackOff, 6/8 pods) because InitAuthConfig() panics when the IAM application or cert is not found. Changed all panic() calls to log warnings and return gracefully, allowing the service to start with auth features disabled. This lets pods stabilize while IAM configuration is being set up. Also adds billing usage record writer for invoice reconciliation.
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.
Summary
InitAuthConfig()frompanic()to log-and-return when IAM application or cert is not foundhanzo-cloud-client-idIAM appRoot Cause
The
init()function incontrollers/account.gocallsInitAuthConfig()which panics if the IAM application specified in config doesn't exist. When the newer image (post v1.766.4) was deployed, it referencedhanzo-cloud-client-idwhich had not been created in IAM yet, causing all pods to crash on startup.Fix
Replace
panic()withfmt.Printf("[WARN]...")+return. The service starts with auth features disabled but remains available for other endpoints (search, chat, etc).Test plan