Affected area
Auth
Supabase CLI version
v2.106.0
Operating system
macOS
Installation method
npm
Command
npx supabase@2.106.0 config push
Actual output
cannot push config: a [remotes.*] block targets project ***, which config push does not yet support. Remove the matching [remotes.*] block, or run config push from a config without it.
Expected behavior
It should push the config matching remotes blocks with project id or passed project-ref. It works fine with v2.105.0 but throws error in version > 2.106.0.
Steps to reproduce
- Create local config.toml file
- Add remotes block for different existing project refs
e.g.
[remotes.dev]
project_id = "dev-project-ref"
[remotes.dev.auth]
site_url = "https://dev.example.com"
additional_redirect_urls = [
"https://dev.example.com/auth/update-password",
]
[remotes.test]
project_id = "test-project-ref"
[remotes.test.auth]
site_url = "https://test.example.com"
additional_redirect_urls = [
"https://test.example.com/",
"https://test.example.com/auth/update-password",
]
- Try command
supabase config push --project-ref "dev-project-ref", it throws error immediately
- To verify it works with v2.105.0, try with command
npx supabase@2.105.0 config push --project-ref="dev-project-ref" and it works as exected, checking and pushing the config
Crash report ID
No response
Docker and service versions
Additional context
No response
Affected area
Auth
Supabase CLI version
v2.106.0
Operating system
macOS
Installation method
npm
Command
Actual output
Expected behavior
It should push the config matching remotes blocks with project id or passed project-ref. It works fine with v2.105.0 but throws error in version > 2.106.0.
Steps to reproduce
e.g.
supabase config push --project-ref "dev-project-ref", it throws error immediatelynpx supabase@2.105.0 config push --project-ref="dev-project-ref"and it works as exected, checking and pushing the configCrash report ID
No response
Docker and service versions
Additional context
No response