fix(proxy): Enable partial matching for User ID filter in virtual keys page #12205
+160
−24
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
fix(proxy): Enable partial matching for User ID filter in virtual keys page
Relevant issues
Fixes LIT-268
Pre-Submission checklist
tests/litellm/
directory, Adding at least 1 test is a hard requirement - see detailsmake test-unit
Type
🐛 Bug Fix
Changes
Problem
The virtual key page (/ui/?page=api-keys) required users to enter the complete, exact User ID to filter results. Partial searches returned no results, making it difficult to find keys when users only remembered part of a User ID.
Solution
Updated the
_list_key_helper
function inkey_management_endpoints.py
to use Prisma'scontains
operator with case-insensitive mode for user_id filtering instead of exact matching.Implementation Details
{"contains": user_id, "mode": "insensitive"}
test_list_key_helper_user_id_partial_matching
Testing
Added tests to verify:
Test passing locally: