Produces invalid configuration snippet

[syntaxaire]

Bug report

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

Describe the bug

When supabase CLI command produces a sample TOML fragment for the CLI user, it can be invalid.

To Reproduce

1. Have a supabase database configuration in local source control which does not match the remote supabase.
2. Run supabase link and select the remote supabase.

Expected behavior

Would print

Local config differs from linked project. Try updating supabase/config.toml
[db.pooler]
enabled = false
port = 54329
pool_mode = "transaction"
default_pool_size = 15
max_client_conn = 100

Actual behaviour

Prints

Local config differs from linked project. Try updating supabase/config.toml
["db.pooler"]
enabled = false
port = 54329
pool_mode = "transaction"
default_pool_size = 15
max_client_conn = 100

The extra " characters in ["db.pooler"] are invalid and will be rejected by supabase CLI if pasted into config.toml as suggested. If the suggested text is used the error message will be

Unknown config fields: ["db.pooler" "db.pooler".enabled "db.pooler".port "db.pooler".pool_mode "db.pooler".default_pool_size "db.pooler".max_client_conn]

System information

• OS: Linux
• supabase CLI version: 1.151.1