Feature request: let Postgres call its own Edge Functions on every branch, with no hand-copied URLs or keys

Supabase's own guides for calling an Edge Function from Postgres (Scheduling Edge Functions, Automatic embeddings) all follow one pattern: pg_cron → pg_net → the project URL and a key read from Vault. Every step of that pattern assumes one hand-configured project. With Branching, it breaks down. 1. Postgres cannot learn its own API URL • An Edge Function gets SUPABASE_URL automatically. Postgres gets nothing, so every guide has you paste into vault.create_secret(...) by hand ([discussion #12813]( has asked about this for years). • A preview branch gets a new project ref at creation time, so no value in config.toml or a dotenvx file can name it ahead of time. [remotes.<branch>.db.vault] covers persistent branches only. • Locally, the URL that works from inside Postgres is a host the CLI hard-codes and the docs mention only in passing. It differs from the SUPABASE_URL the local functions see. • The workarounds people use are a CI step that c…