feat: add custom configuration to pass it as constructor param for a CustomGuardrail
#8307
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.
Add dedicated configuration for custom GuardRail.
A proposition to add custom configuration to pass it as constructor param in dynamic instanciation of a
CustomGuardrail
, as has been done for others 'ENTERPRISE' guardrails implementations.Permit to define a default global configuration in yaml to set default parameters for a custom guardrail.
Example :
This PR follows a discussion with @superpoussin22,
Type
🆕 New Feature
Changes
CustomConfig
inlitellm/litellm/types/guardrails.py L109
.custom_config=litellm_params["custom_config"]
in dynamic construction of instanceCustomGuardrail
inlitellm/litellm/proxy/guardrails/init_guardrails.py L155
.