fix(deploy): fix SELF_SIGNED_CERT_IN_CHAIN in production migration containers#996
Merged
zbigniewsobiecki merged 1 commit intodevfrom Mar 23, 2026
Merged
Conversation
…ntainers 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>
This was referenced Mar 23, 2026
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
--env-file /opt/services/cascade.envwhich doesn't containDATABASE_SSL, causinggetDb()to fail withSELF_SIGNED_CERT_IN_CHAINagainst Supabase's connection pooler--env-filewith explicit-e DATABASE_SSL=falseon the three migration containers (drizzle-kit migrate,migrate-triggers.ts,migrate-hooks.ts)-e DATABASE_SSL=falseto the re-encrypt step (keeps--env-fileforCREDENTIAL_MASTER_KEY)DATABASE_SSL=falseinto/opt/services/cascade.envbefore service restarts, ensuring the router and dashboard also pick it upTest plan
main— all three migration steps pass withoutSELF_SIGNED_CERT_IN_CHAINcascade-routerandcascade-dashboardcome up healthy after deploy🤖 Generated with Claude Code