[Bug]: Can't rotate master key in open source version

[l-austenfeld]

What happened?

When trying to rotate the master key as described in the docs (https://docs.litellm.ai/docs/proxy/master_key_rotations) I get an error stating that rotating virtual keys is an enterprise feature.

I am assuming this is a bug in the license checking code since the error message only mentions virtual keys and the docs do not mention that rotating the master key is an enterprise feature (in contrast to virtual key rotations which has a clear header - see https://docs.litellm.ai/docs/proxy/virtual_keys#-key-rotations).

If this is intended behavior, please update the docs and error message to prevent confusion.

Relevant log output

❯ curl -L -X POST 'http://localhost:4000/key/regenerate' \
-H 'Authorization: Bearer sk-1234' \
-H 'Content-Type: application/json' \
-d '{
  "key": "sk-1234",
  "new_master_key": "sk-PIp1h0RekR"
}'
{"error":{"message":"Internal Server Error, Regenerating Virtual Keys is an Enterprise feature, You must be a LiteLLM Enterprise user to use this feature. If you have a license please set `LITELLM_LICENSE` in your env. Get a 7 day trial key here: https://www.litellm.ai/#trial. \nPricing: https://www.litellm.ai/#pricing","type":"internal_server_error","param":"None","code":"500"}}%

Are you a ML Ops Team?

No

What LiteLLM version are you on ?

85525c5 (latest commit at time of writing)

Twitter / LinkedIn details

No response

[ishaan-jaff]

cc @krrishdholakia do you know, is this supposed to be an enterprise feature ?

[krrishdholakia]

The regenerate endpoint is an Enterprise feature, so it should be called out on the rotating master key doc as well.

Ideally there's a way we can offer master key rotations on OSS so people aren't blocked - maybe a script or special flag?

[krrishdholakia]

Added a special check for new_master_key field - if set, we won't enforce the license check. This allows master key rotations to happen on OSS.