Add supabase config pull command

[robwhess]

It's often easier for me to update project settings in the Supabase dashboard. However, if I do that, there's no easy way to automatically synchronize those updates to my local Supabase config in config.toml. Others have noted this lack of functionality, too, e.g. #22455. The Supabase CLI already has the command supabase config push to push changes from the local config to production. It'd be awesome if you added a supabase config pull command to pull changes made in the dashboard to the local config.

[BertVanHecke]

+1

[ghost]

Yes, please!

[danoc]

In addition to pushing and pulling, it'd be great if there was a command that could exit with an error (1) exit code if there is drift between the local and remote configs.

[H0lz3r-x64]

Bump!

[marcus-rev]

Our team would also find this functionality very useful.

[xidsyed]

+1. make it a completely version controlled automated system!

[nassmim]

+1

[StefanEissler]

+1

[Michota]

Sorry for asking there, may be not valid place.

Am I the only one that gets no config.toml when using supbase link?
Instead I get this thing in terminal (i have no config.toml so there should be no differences really).

WARNING: Local config differs from linked project. Try updating supabase/config.toml
diff supabase/config.toml blmiyfsimvaiufnnqhbh
--- supabase/config.toml
+++ blmiyfsimvaiufnnqhbh
@@ -58,8 +58,8 @@
 
 [auth]
 enabled = true
-site_url = "http://127.0.0.1:3000"
-additional_redirect_urls = ["https://127.0.0.1:3000"]
+site_url = "http://localhost:3000"
+additional_redirect_urls = []
 jwt_expiry = 3600
 enable_refresh_token_rotation = true
 refresh_token_reuse_interval = 10
@@ -101,9 +101,9 @@
 [auth.email]
 enable_signup = true
 double_confirm_changes = true
-enable_confirmations = false
+enable_confirmations = true
 secure_password_change = false
-max_frequency = "1s"
+max_frequency = "1m0s"
 otp_length = 6
 otp_expiry = 3600
 [auth.email.template]

[StefanEissler]

This is similar to the discussion here.
The idea is that there is the possibility to have a "supabase config pull" request, which applies changes in remote to the local project and replaces the local config.toml - or that on linking, changes in remote automatically get applied in the local config.toml file. So they can stay in sync more easily.
Now you have to manually apply all the changes which get shown in your terminal. When managing multiple project this happens quite often and is frustrating...

[tamaro-skaljic]

yes please

[craig-at-metashield-io]

interestingly enough, when you run supabase config push, it does generate and display a diff of the local config.toml file and the remote settings, before asking for confirmation.
given that, i say "No' and then reverse that diff into the local config.

hella round-about and i wouldn't want to do this frequently, but it does work.

[grokpot]

➡️➡️➡️ VISUAL CAPS SO EVERYONE SEES IT ⬅️⬅️⬅️

this work - just don't accidentally press 'y' 😆

[Mark-Life]

+1

[bhishekprajapati]

+1

[LouisCapelle]

+1