Vercel Integration & Database Branching

[alexbaron-me]

I'm trying to set up a Redwood project using the new database branching feature.
However, Vercel's preview builds all connect to the main database branch, as opposed to the newly created preview one. This is because Supabase's Vercel integration does not modify the environment variables for preview builds, passing the production database connection string.
My current workaround uses the management API to generate the connection string for the preview branch, but that does not seem like a stable solution.

Am I overlooking something?

[jbojcic1]

I have the same issue. I doesn't seem like it's supposed to be like that because the docs here say Supabase automatically updates your Vercel project with the correct environment variables for the corresponding preview branches.

[danihenrique]

Same issue here!
Basically the PREVIEW variables has the same values after Supabase sync the ENVS.
But, if you look at the Branchs session on the Interface, and click on "Connect", my branch has a different API KEY and URL.
That's the values should be added on the PREVIEW variables?
Any way, I tried manually update and didn't work, so maybe it's not that or just that.

[jbojcic1]

According to this we are supposed to be seeing these branches as preview environments in Vercel but I am not seeing that.

[sweatybridge]

Did you guys create the supabase project from vercel marketplace or added the vercel integration from supabase dashboard?

Branching might be buggy for vercel marketplace since it's something new. But I can try to help if you explain your setup a bit more.

[Schwefelhexa]

I added the integration from the supabase dashboard.
Basically, I have a Redwood project (using Prisma as the ORM) deployed to Vercel, where any open PR gets a live preview hosted on Vercel. The integration with Supabase worked insofar that a new DB branch is also created whenever a PR is opened.
However, the env variables of the Vercel preview deployment are the same as in the production one, meaning the Redwood preview deployment uses the connection string for the production database.
Expected behavior (imo) would be for the env variables to change in preview deployments, pointing to the newly-created branch.

[sweatybridge]

Ok, thanks for clarifying. This is worth opening a support ticket so I can look into your project on a case by case basis.

https://supabase.com/dashboard/support/new

Say in the ticket you want to be routed to Dev Workflows team so I can be assigned automatically.

[sweatybridge]

Also, could you try closing and re-opening the PR? Because according to our docs

The synchronization happens at the time of Pull Request being opened, not at the time of branch creation.

https://supabase.com/docs/guides/deployment/branching?queryGroups=platform&platform=existing#vercel

[jbojcic1]

I tried that multiple times but doesn't help

[jbojcic1]

@sweatybridge I created the organization and project from Vercel and then I went to Supabase and enabled branching there

[sweatybridge]

Could you try closing and re-opening the PR? Because according to our docs

The synchronization happens at the time of Pull Request being opened, not at the time of branch creation.

[jbojcic1]

I tried that multiple times but doesn't help

[jbojcic1]

@sweatybridge any luck? I created the ticket for the support and asked to be routed to you as instructed. 2 days ago they said they will share it with you. Hopefully they did.

[sweatybridge]

I've updated branching docs to elaborate on the extra steps required to connect supabase project to vercel https://supabase.com/docs/guides/deployment/branching?queryGroups=platform&platform=existing#vercel

Hope this helps.