Vault secrets table grants missing on remote despite migration
Hey everyone — I'm running into an issue with Supabase migrations.
I have a local setup with a single init migration that includes explicit GRANT statements for the vault.secrets table (e.g., GRANT INSERT, UPDATE ON vault.secrets TO service_role). On local, everything works and the grants are applied correctly.
However, when the same migration is applied on the remote project (via Supabase’s branching workflow), the grants for service_role are not applied. I did not use db push or db pull at any point — only the migration SQL file.
I’ve verified that:
The vault.secrets table is created in the migration.
The grants are included after the table creation in the same file.
The service_role still lacks INSERT/UPDATE privileges on remote.
Is there something special about the vault schema that blocks permission grants remotely? Or are there known limitations in applying grants through migrations in remote Supabase environments?
Any insights or workarounds appreciated! Thanks
I have a local setup with a single init migration that includes explicit GRANT statements for the vault.secrets table (e.g., GRANT INSERT, UPDATE ON vault.secrets TO service_role). On local, everything works and the grants are applied correctly.
However, when the same migration is applied on the remote project (via Supabase’s branching workflow), the grants for service_role are not applied. I did not use db push or db pull at any point — only the migration SQL file.
I’ve verified that:
The vault.secrets table is created in the migration.
The grants are included after the table creation in the same file.
The service_role still lacks INSERT/UPDATE privileges on remote.
Is there something special about the vault schema that blocks permission grants remotely? Or are there known limitations in applying grants through migrations in remote Supabase environments?
Any insights or workarounds appreciated! Thanks
