Repository navigation
Rotate the production secrets - #329
Merged
Merged
Conversation
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
OpenTofu plan for
|
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
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.
Why
The API started on AWS with interim secrets. The real values, freshly issued, are now on the
productionenvironment, and version 3 writes them.What changes
app_secrets_version2 → 3. The deploy rewrites every SecureString from theproductionsecrets, and the service rolls a new task.The new values are the Discord bot token and client secret, the Mailgun and Skylink keys, and a refreshed tunnel token, all reset on 10 Nov. The JWT pair,
ADSB_API_TOKENand the webhook URL keep their values.After merging
🤖 Generated with Claude Code