feat: enhance custom guardrail functionality with dynamic HTTP headers #16785
+505
−80
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
- Added support for passing custom HTTP headers to the guardrail API via the `get_guardrail_custom_headers` method. - Updated GraySwan guardrail to utilize custom headers in API requests. - Improved documentation for custom guardrail usage, including examples for dynamic header configuration. - Refactored payload preparation to prioritize custom headers over dynamic body parameters and configuration values. - Added comprehensive tests for custom header extraction and payload preparation logic.
|
@agrattan0820 is attempting to deploy a commit to the CLERKIEAI Team on Vercel. A member of the Team first needs to authorize it. |
…guardrail payload handling - Enhanced the S3 cache test to verify that all expected keys are present during concurrent operations. - Updated the GraySwan guardrail tests to ensure custom headers are ignored for configuration parameters, prioritizing dynamic body values instead. - Removed outdated tests related to custom header merging that are no longer applicable.
Contributor
|
@agrattan0820 looks like your testing is failing 
|
…paration - Refactored test functions for better readability and consistency by applying uniform formatting. - Updated the GraySwan guardrail's payload preparation to include an optional `custom_headers` parameter. - Improved assertions in tests to ensure accurate verification of expected behavior regarding custom headers and dynamic body values.
Author
Yep yep, pushing up the working commit! |
- Removed unnecessary line breaks and streamlined conditional expressions for better clarity. - Consolidated multiple lines into single lines where appropriate to enhance code conciseness. - Ensured consistent formatting across various sections of the file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Enhance custom guardrail functionality with dynamic HTTP headers
Relevant issues
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
✅ Test
Changes
get_guardrail_custom_headersmethod.