Sync s3 keys with vercel
I am making use of the great vercel and github integration so that if I create a new feature branch I get a vercel deployment as well as a supabase branch and the env vars for the supabase branch are synced across to vercel so it points to the right supabase branch.
However, it does not sync across any s3 keys. I am using the s3 client for supabase storage. I notice that actually unlike with local dev there are no access keys created automatically on preview deployments.
Is there a way to have this set up so that I don't have to manually create s3 keys for each new feat branch and then also update them in the vercel environment?
3 Replies
when you say using the s3 client, are uou using supabase storage or are you using s3?
If the former, i think you need to set up buckets for the new environment anyway so and so the s3 keys being copied over would not help as you need to set up environment variables for those buckets
I'm using supabase storage but connecting to it using the s3 protocool. The buckets all get setup either via the config.toml or through migrations
currently for your vercel integration are you manually adding the environment variables for your access key and secret key for the main branch i.e supabase is not passing those values in like it does for other variables
Given you said access/secret keys are created manually via the supabase ui after a branch is created i suspect that you can't have them in vercel as those variables are only things that exist at branch creation
this might be a good feature request if you select feedback -> share an idea in the top of the dashboard