scriptoriumadmin/litellm
1
0
Fork 0
mirror of https://github.com/BerriAI/litellm.git synced 2026-10-07 02:59:05 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 103

docs: improve comment clarity per Greptile feedback

Browse source 
Restructure comments to make the intent clearer:
- First function: matches/tracks policies (may find nothing)
- Second function: always runs independent resolution (may find inherited guardrails)

This makes it clear why both functions must always be called.
This commit is contained in:
Julio Quinteros Pro 2026-02-14 14:42:54 -03:00
parent 0f0b7a3f50
commit 3b7cc1d138
1 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
litellm/proxy/litellm_pre_call_utils.py
View file

@ -1704,12 +1704,12 @@ def add_guardrails_from_policy_engine(
f"key_alias={context.key_alias}, model={context.model}, tags={context.tags}"
)
# Match and track policies (may be empty, but resolution still happens)
# Match and track policies based on attachments and request body
_match_and_track_policies(data, context, request_body_policies)
# Apply resolved guardrails to metadata
# Note: PolicyResolver does its own independent matching and inheritance resolution,
# so we always call it even if applied_policy_names is empty
# Always resolve and apply guardrails, even if no policies matched above.
# PolicyResolver does its own independent matching and inheritance resolution,
# so guardrails can still be applied via inherited parent policies.
_apply_resolved_guardrails_to_metadata(data, metadata_variable_name, context)