Skip to content

fix(ci): pass per-app SENTRY_DSN secrets to the staging secret renderer - #5

Merged
Afgan0r merged 1 commit into
masterfrom
feat/wire-sentry-dsn-deploy-env
Jun 15, 2026
Merged

fix(ci): pass per-app SENTRY_DSN secrets to the staging secret renderer#5
Afgan0r merged 1 commit into
masterfrom
feat/wire-sentry-dsn-deploy-env

Conversation

@Afgan0r

@Afgan0r Afgan0r commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

The deploy-staging Render and apply staging secrets step never passed any SENTRY_DSN env to the renderer, so SENTRY_DSN was rendered empty in all runtime Secrets (verified: cluster secrets have no SENTRY_DSN). The Phase 18 wiring was incomplete. This passes the three per-app secrets so each app's runtime Secret carries its DSN. Completes #4.

🤖 Generated with Claude Code

The "Render and apply staging secrets" step never passed any SENTRY_DSN env to
render-staging-secrets.py, so SENTRY_DSN was always rendered empty in the runtime
Secrets (the Phase 18 wiring was incomplete). Pass the three per-app secrets
SENTRY_DSN_SERVER_2 / _REPLAYS_FETCHER / _REPLAY_PARSER_2 so each app's runtime
Secret carries its DSN. Completes the per-app wiring from the prior renderer change.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Afgan0r
Afgan0r merged commit 2f2cfc6 into master Jun 15, 2026
3 checks passed
@Afgan0r
Afgan0r deleted the feat/wire-sentry-dsn-deploy-env branch June 15, 2026 14:50
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