8 views
-/https://github.com/berriai/litellm/issues/34379
GitHub · issue

#34379 [Bug]: The blocked field cannot be set to false on customers.

  • State: open
  • Author: @larskraemer
  • Labels: bug, proxy

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

In `customer_endpoints.py`, `update_end_user`: ``` non_default_values = {} for k, v in data_json.items(): if v is not None and v not in ( [], {}, 0, ): # models default to [], spend defaults to 0, we should not reset these values non_default_values[k] = v ``` This will strip out `blocked: False`, as well as things like `max_budget: 0` from updates to customers. This also means that it is possible to block a customer via the API, but not to unblock them.

### Steps to Reproduce

1. Block a customer 2. Try to unblock said customer by POST /customer/update 3. Observe that they stay blocked

### Relevant log output

```shell

```

### What part of LiteLLM is this about?

Proxy

### What LiteLLM version are you on ?

v1.92.0

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d18h27m48s ago — entered · #import:https:::github.com:berriai:litellm post #2485
The left issue is a localized update-semantics fix with focused regression tests. The right requires security-sensitive authorization changes across request validation, persistence, secret resolution, compatibility behavior, and broader regression testing, creating substantially greater implementation risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search