Skip to content
This repository was archived by the owner on Jul 9, 2026. It is now read-only.

Rename SUPABASE_SERVICE_KEY to SUPABASE_SECRET_KEY - #115

Merged
anth-volk merged 1 commit into
mainfrom
fix/fix-deploy-errors
Mar 10, 2026
Merged

Rename SUPABASE_SERVICE_KEY to SUPABASE_SECRET_KEY#115
anth-volk merged 1 commit into
mainfrom
fix/fix-deploy-errors

Conversation

@anth-volk

Copy link
Copy Markdown
Contributor

Summary

  • Rename SUPABASE_SERVICE_KEYSUPABASE_SECRET_KEY across 18 files to align with Supabase's new key naming
  • Add the secret key to Terraform and deploy pipeline (was missing entirely — production had no access)
  • Add to Modal secrets sync so serverless functions get the key

Fixes #114

Test plan

  • Verify zero remaining references to old name: grep -r SUPABASE_SERVICE_KEY .
  • Verify SUPABASE_SECRET_KEY GitHub Actions secret is set
  • Terraform plan shows new SUPABASE_SECRET_KEY env var on Cloud Run
  • db-reset workflow succeeds with new secret name
  • Modal functions can perform admin storage operations

🤖 Generated with Claude Code

Align with Supabase's new key naming (service_role → secret key).
Also adds the secret key to Terraform, deploy.yml, and Modal
secrets sync — it was previously missing from the production
deploy pipeline entirely.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@anth-volk
anth-volk marked this pull request as ready for review March 10, 2026 20:53
@anth-volk
anth-volk merged commit 1ee6a22 into main Mar 10, 2026
5 checks passed
@anth-volk
anth-volk deleted the fix/fix-deploy-errors branch March 10, 2026 20:54
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rename SUPABASE_SERVICE_KEY to SUPABASE_SECRET_KEY and add to deploy pipeline

1 participant