Skip to content

fix(deploy): fix SELF_SIGNED_CERT_IN_CHAIN in production migration containers#997

Merged
zbigniewsobiecki merged 1 commit intomainfrom
dev
Mar 23, 2026
Merged

fix(deploy): fix SELF_SIGNED_CERT_IN_CHAIN in production migration containers#997
zbigniewsobiecki merged 1 commit intomainfrom
dev

Conversation

@zbigniewsobiecki
Copy link
Copy Markdown
Member

Merges dev → main.

Includes #996: migration containers were using --env-file without DATABASE_SSL, causing getDb() to fail with SELF_SIGNED_CERT_IN_CHAIN against Supabase. Fixes by passing -e DATABASE_SSL=false explicitly to all migration steps and injecting it into cascade.env before service restarts.

🤖 Generated with Claude Code

…ntainers (#996)

Migration steps were using --env-file /opt/services/cascade.env which
doesn't contain DATABASE_SSL, causing getDb() to fail with
SELF_SIGNED_CERT_IN_CHAIN against Supabase's connection pooler.

- Replace --env-file with explicit -e DATABASE_SSL=false on the three
  migration containers (drizzle-kit, migrate-triggers, migrate-hooks)
- Add -e DATABASE_SSL=false to the re-encrypt step (keeps --env-file for
  CREDENTIAL_MASTER_KEY)
- Add "Configure DATABASE_SSL for production" step that idempotently
  injects DATABASE_SSL=false into /opt/services/cascade.env before
  service restarts, so router and dashboard also get it

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
@zbigniewsobiecki zbigniewsobiecki merged commit 5dccbd1 into main Mar 23, 2026
15 checks passed
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