[db.vault] config not syncing with remote project
Hello, I am using the [db.vault] config in config.toml to be able to set secret in vault. It is working ok in local, this means when I do
pnpx supabase migration up it update vault secrets that I defined under the [db.vault] section.
I am trying to make it work with my dev remote project but found no success in it.
I tried:
pnpx supabase link --project-ref xxxxxxx --password xxxxxx to link the remote dev project, then use:
pnpx supabase db push xxxxxx --password xxxxx --include-seed --yes --include-all --linked as stated here https://github.com/orgs/supabase/discussions/12813#discussioncomment-12245622 but found no success.
Also tried:
pnpx supabase config push --yes --experimental it does not seem to work, the config is not syncing with remote project (was unable to disable http api even tho I set:
Again, it worked locally but not on the remote projectGitHub
Environment variables for DB functions · supabase · Discussion #1...
Update: it's on our roadmap Hi, I'm currently working through the User Management on React Tutorial and in the Storage Management section code example, the project URL and service role key ...
8 Replies
where did you find about
[db.vault]? I haven't seen that config before...For some reason the link I provided above does not open on the right comment so here it is
ooh wow, this is cool! did not new about it, and is not documented on the config ref yet...
what cli version you are using?
cli version 2.31.4
ok, after testing (v 2.31.8), the only way I was able to make the secret to be created was by having a migration to be applied
Thx a lot, I'll check that tomorrow at work and see if I can make it work
It works, it is not optimal at all since I have to add empty migration each time we want to add secret but at least we can keep working.
It would be a good thing to add to the
pnpx supabase config push, altho I don't know how feasable it isI know a contributor is working on an improvement here, so will keep you posted!