mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-13 23:11:40 +00:00
559fa91304
The edit form's "app may not match upstream" warning only fired when a client was sitting in the form, so a stored app (redacted to null by the GET) never triggered it: an admin could repoint a client-forwarded server at a different upstream and silently keep an app registered for the old one. The backend now stamps a non-secret has_configured_client boolean on redacted responses (derived from the credentials blob at redaction time, or from the registry's decrypted client_id on the list path, whose table objects never carry the blob). The non-admin and virtual-key sanitizers null it back out; only the admin edit form needs it. The edit form fires the warning from the flag when the credential class is unchanged (a cross-class switch replaces the stored app, so nothing kept can mismatch), and the banner hides while the remove-app checkbox is checked since removal writes an explicit-null credential |
||
|---|---|---|
| .. | ||
| litellm-dashboard | ||
| Dockerfile | ||
| nginx.conf | ||