Skip to content

feat(chart): inject the four remaining API keys from the Secret - #12

Merged
dangerousplay merged 1 commit into
mainfrom
chart/api-key-secrets-main
Aug 23, 2026
Merged

dangerousplay merged 1 commit into
mainfrom
chart/api-key-secrets-main

Conversation

@dangerousplay

Copy link
Copy Markdown
Collaborator

CB_ANTHROPIC_API_KEY, CB_OPENAI_API_KEY and the Google Search pair were the only credentials the chart knew how to reference. The YouTube, SauceNAO, AudD and exchangerate keys had no path in at all — and config.extraEnv is the wrong one, because it renders into the ConfigMap, so a values file in Git would hold the plaintext.

Same guard as the existing four: an unset key is not injected, and the feature then answers its "not found" string rather than erroring.

helm template with the keys set puts CB_YOUTUBE_API_KEY, CB_SAUCENAO_API_KEY and CB_EXCHANGERATE_API_KEY in all three Deployments and the migrate Job.

Needed by cookiebot-uat, which now holds the values in its cookiebot-secrets Secret.

🤖 Generated with Claude Code

CB_ANTHROPIC_API_KEY, CB_OPENAI_API_KEY and the Google Search pair were the
only credentials the chart knew how to reference. The YouTube, SauceNAO, AudD
and exchangerate keys had no path in at all, and config.extraEnv is the wrong
one -- it renders into the ConfigMap, so a values file in Git would hold the
plaintext.

Same guard as the existing four: an unset key is not injected, and the feature
then answers its "not found" string rather than erroring.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@dangerousplay
dangerousplay merged commit 1aa8c83 into main Aug 23, 2026
9 checks passed
@dangerousplay
dangerousplay deleted the chart/api-key-secrets-main branch August 23, 2026 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant