From 8933969af440fdcb1d5053a9ea795564cfec7037 Mon Sep 17 00:00:00 2001 From: lior-k Date: Thu, 25 Jun 2026 11:09:05 +0300 Subject: [PATCH] fix(guardrails): enable allow_request_metadata_override in alice test config The config comment stated app_id is supplied per-request via metadata but allow_request_metadata_override was absent (defaults false), so every call would fail to resolve app_id and return HTTP 500. --- tests/local_testing/test_configs/test_alice_config.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tests/local_testing/test_configs/test_alice_config.yaml b/tests/local_testing/test_configs/test_alice_config.yaml index c34d192e33a..b9ea678e579 100644 --- a/tests/local_testing/test_configs/test_alice_config.yaml +++ b/tests/local_testing/test_configs/test_alice_config.yaml @@ -10,7 +10,7 @@ guardrails: guardrail: alice_wonderfence mode: ["during_call", "post_call"] # Test both input and output api_key: os.environ/ALICE_API_KEY - # app_id is supplied per-request via metadata.alice_wonderfence_app_id (not at static litellm_params level) + allow_request_metadata_override: true # app_id supplied per-request via metadata.alice_wonderfence_app_id api_timeout: 20.0 # Timeout in seconds (default: 20.0) platform: aws # Optional: Cloud platform (aws, azure, databricks, etc.) default_on: true