(feat) Support 'guaranteed_throughput' when setting limits on keys belonging to a team #15120
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…hen creating tpm/rpm limits on keys prevents overallocating tpm/rpm limits
…for model specific tpm / rpm limits prevents admin from granting keys more tpm/rpm than created for a key
…put on key update and service account key creation
allows user to set the type of tpm/rpm limit they're trying to set
…oughput/best effort throughput on key
…oss create + edit key
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title
(feat) Support 'guaranteed_throughput' when setting limits on keys belonging to a team
Relevant issues
Prevents admin from accidentally overallocating tpm/rpm limit to a key - also covers model specific tpm/rpm limits
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🆕 New Feature
Changes