Skip to content

Fix: Use SUPABASE_DB_URL in db-reset workflow#137

Merged
anth-volk merged 5 commits intomainfrom
fix/fix-integ-test
Mar 16, 2026
Merged

Fix: Use SUPABASE_DB_URL in db-reset workflow#137
anth-volk merged 5 commits intomainfrom
fix/fix-integ-test

Conversation

@anth-volk
Copy link
Copy Markdown
Contributor

Summary

  • Replace all SUPABASE_POOLER_URL references in db-reset.yml with SUPABASE_DB_URL
  • The SUPABASE_POOLER_URL secret was stale (last updated Dec 2025) and had the wrong password
  • Aligns the db-reset workflow with the same env var convention used in deploy.yml and all other workflows

Test plan

  • Run db-reset workflow against production and confirm it connects successfully

🤖 Generated with Claude Code

anth-volk and others added 4 commits March 16, 2026 23:56
The staging/testing database may only have one country seeded.
Change assertion from >= 2 to >= 1 so the test validates the
endpoint works without assuming a specific seed preset.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Add target input (staging/production) so the workflow can reset
either database. Confirmation string changes per target
(reset-staging vs reset-prod). Validate job now tests connectivity
against both environments using a matrix. All secrets resolve from
the selected environment.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
@anth-volk anth-volk marked this pull request as ready for review March 16, 2026 23:19
@anth-volk anth-volk merged commit 5166da3 into main Mar 16, 2026
6 checks passed
@anth-volk anth-volk deleted the fix/fix-integ-test branch March 16, 2026 23:19
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