mirror of
https://github.com/BerriAI/litellm.git
synced 2026-09-15 23:31:29 +00:00
c893187374
Switching an endpoint between always-on and opt-in landed on the card last
commit, but removing one still meant leaving for the Guardrails page, which is
the trip the card was supposed to save. Each row now carries a delete action
that opens the same DeleteResourceModal the Guardrails table uses, so the
confirmation looks identical wherever it is triggered from, and it names the
endpoint, its id, its api base, and whether it currently applies to every
request. The warning above those details depends on the mode, since the two
modes fail differently: deleting an always-on endpoint silently stops
compressing and input costs go back up, while deleting an opt-in one breaks
the callers that name it in their request body.
Delete is gated exactly like the mode select, on admin and not
config-file-defined, matching DELETE /guardrails/{id} and the disabled Delete
item the guardrail table already shows for config guardrails.
The card body grew past the point where one component could hold it, so the
add form and the delete confirmation moved into their own components. The form
owns its own fields now, which drops four pieces of state from the tab and
means a failed create keeps what was typed instead of the tab having to
remember it.
|
||
|---|---|---|
| .. | ||
| litellm-dashboard | ||
| Dockerfile | ||
| nginx.conf | ||