Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Secrets defined in edge_runtime.secrets are not propagated when supabase config push is run. I'm not 100% sure if it's a bug, or just lack of documentation, but I found that behavior very confusing. I found no information about this parameter here nor here, nor even in GitHub issues. Nevertheless, that config exists in the initial config.toml and populates the secrets in the edge runtime when run locally.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Define edge_runtime.secrets and remotes.<name>.edge_runtime.secrets.

   [edge_runtime.secrets]
   FOO = "foo"
   [remotes.production.edge_runtime.secrets]
   FOO = "env(FOO)"

2. Run supabase config push for the remote.
3. Go to https://supabase.com/dashboard/project/_/functions/secrets and observe that the secrets were not added.

Expected behavior

The secrets are populated OR it's explicitly mentioned in the documentation that these won't be populated on supabase config push. A comment in the initial config.toml near [edge_runtime.secrets] could also be useful.

Screenshots

System information

• OS: macOS
• Browser (if applies): -
• Version of supabase-js: -
• Version of Node.js: -
• Version of Supabase CLI: 2.90.0

Additional context