Ian Copp

> We now support declaring vault secrets in `config.toml` so you can reference them directly in migration or seed file when applying with `supabase db push --include-seed`. For eg. > > * in `.env.local` > > ```dotenv > MY_PROJECT_REF="abc" > MY_ANON_KEY="def" > ``` > > * in `supabase/config.toml` > > ```toml > [db.vault] > my_project_ref = "env(MY_PROJECT_REF)" > my_anon_key = "env(MY_ANON_KEY)" > ``` Okay, but what about for branching? That's a key point of the original ask, and Supabase still keeps putting static values in all the examples and docs files for things like this.

"Store them in your Vercel environment once"... how? There's no option to set your own value for the S3 access key ID / secret access key, it's randomly generated.

How do I seed storage objects with `user_metadata` values? For example, I've got this in `config.toml`. ``` [storage.buckets.assets] public = false objects_path = "./buckets/assets" ``` Each file should end up with a couple of `user_metadata` properties. I already tried pre-writing rows to `storage.objects` (doesn't work, they get overwritten), and there's no way for me to update those rows afterwards because the seed sql files only run before storage objects are added.