docs: expand clowder/database annotation reconciliation details#1784
Open
mjholder wants to merge 2 commits into
Open
docs: expand clowder/database annotation reconciliation details#1784mjholder wants to merge 2 commits into
mjholder wants to merge 2 commits into
Conversation
Clarify how the two-tier secret lookup works in app-interface mode (annotation-first, hostname fallback) and why the annotation is required for database restore/migration scenarios where the RDS hostname does not follow the expected naming pattern. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Show the ClowdApp and app-interface resource side by side to make it clear the annotation value matches .metadata.name, not database.name. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
Author
|
/test-e2e |
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
docs/providers/database.mdto explain the two-tier secret lookup (annotation match → hostname fallback), why the annotation is necessary for restore/migration scenarios, and key details like timing and value requirements.Context
Learned from a DR exercise that the existing docs mention the annotation exists but don't explain how the reconciliation logic works or why the hostname fallback fails for restored instances. This caused confusion during a real restore.
Test plan
appinterface.go🤖 Generated with Claude Code