### What happened?

I noticed that new proxy configs were not getting picked up, specifically general_settings, but I suspect it will apply to most of what inside table LiteLLM_Config.

In litellm/proxy/proxy_server.py, the function_update_config_fields is pulling in values from config and overwriting the newly deployed values.

That or the initial update, at deployment time, of that table is just not happening and previous values stay behind, and then the new values get overwritten.

I confirmed this behavior by manually deleting the general_settings row, rollout restating, and then the new values got populated.

### Relevant log output

```shell n/a ```

### Are you a ML Ops Team?

Yes

### What LiteLLM version are you on ?

v1.74.3-stable.patch.3

### Twitter / LinkedIn details

https://www.linkedin.com/in/maarmenta/