New API keys on preview branches not being auto-created
🤷other
Is there anything special we need to do to get our preview branches (which are automatically created using the github integration) to automatically have the new api keys set up? And then sync those api keys to vercel preview branches using the vercel integration?
The expected behavior is I create a new PR on github, supabase registers that, creates the new preview branch, creates the new api keys, then syncs all env vars (including the new api keys) to vercel.
The current behavior is I create a new PR on github, supabase registers that, creates the new preview branch, DOES NOT create the new api keys, then syncs all env vars (EXCLUDING the new api keys) to vercel.
We have api keys enabled on the db that supabase is basing off of, and I haven't seen anything in the config.toml configuration I can edit to auto enable this.
The expected behavior is I create a new PR on github, supabase registers that, creates the new preview branch, creates the new api keys, then syncs all env vars (including the new api keys) to vercel.
The current behavior is I create a new PR on github, supabase registers that, creates the new preview branch, DOES NOT create the new api keys, then syncs all env vars (EXCLUDING the new api keys) to vercel.
We have api keys enabled on the db that supabase is basing off of, and I haven't seen anything in the config.toml configuration I can edit to auto enable this.
