Local secrets overwrite auth provider secrets in cloud

[DuncanLHS]

Describe the bug On npx supabase db push local config from config.toml gets written into my auth provider config on cloud.

To Reproduce Use a social auth provider in the local environment and configure secrets in config.toml Run npx supabase db push

Expected behavior Cloud config remains independent of local config

Screenshots

I have reported this issue some months ago but I think it got lost in with branching issues. The client secret actually remains as set, the id and url get replaced.

[DuncanLHS]

To add, the same happens with redirect urls.

[k1ng-arthur]

I just tried this locally and didn't get the issue you mentioned. I setup github auth and supabase db push did nothing but supabase config push did indeed push the config changes to the remote project. I was wondering if your cli was up to date and this issue still persists