Global Policy Support for LLM Providers and Proxies#2238
Conversation
… yaml; and api key policy not applying globally
|
Important Review skippedToo many files! This PR contains 246 files, which is 96 over the limit of 150. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (246)
You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
285bdbf to
0eabb3a
Compare
0eabb3a to
2ac0e23
Compare
Purpose
Introduces
globalPoliciesandoperationPoliciesas first-class fields on LLM provider and proxy deployment artifacts, replacing the flat policies list. This enables provider-wide policy enforcement — such as a rate limit that applies across all operations — without duplicating configuration per path.Schema change
Artifacts now carry two distinct policy lists:
Gateway version-aware delivery
A new
deploymenttransformpackage handles artifact adaptation at deploy time. Gateways at version ≥ 1.2.0 receive the new globalPolicies/operationPolicies shape; older gateways transparently receive the legacy flattened policies list with the correct apiVersion stamp — no gateway-side change required for backward compatibility.AI Workspace UI
Guardrails tabs updated for both LLM proxies and service providers to surface global vs. per-operation policy configuration.
Version bump
Gateway management API and artifact apiVersion promoted to
v1alpha2; platform-api resource URL promoted tov1alpha2.