© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•14mo ago•
4 replies
J_men

CLI - db push requires unrelated secrets

I have a local instance of supabase with Google OAuth setup. I specify the Google secrets in the toml from a .env file which is ignored in the repo

e.g.
[auth.external.google]
enabled = true
client_id = "env(GOOGLE_CLIENT_ID)"
secret = "env(GOOGLE_SECRET)"
[auth.external.google]
enabled = true
client_id = "env(GOOGLE_CLIENT_ID)"
secret = "env(GOOGLE_SECRET)"


Now when I run the
supabase db push
supabase db push
command in the pipeline to deploy to the remote instance, it complains that these secrets are not present in the toml config. But the Google OAuth values are not required to do a database migration

Is there any way to resolve this, I don't really want to put the secrets into the pipeline when they shouldn't be necessary
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

CLI Issue: supabase db push
SupabaseSSupabase / help-and-questions
3y ago
supabase cli error on pull or push db
SupabaseSSupabase / help-and-questions
5mo ago
db push problem
SupabaseSSupabase / help-and-questions
2mo ago
DB Push Connection Failure
SupabaseSSupabase / help-and-questions
6mo ago