docs(tag-routing): add negation tags and tag_regex sections - #437
Merged
mateo-berri merged 4 commits intoJun 30, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit cc05be7. Configure here.
added 2 commits
June 30, 2026 00:30
…nly pool semantics
…gation vs regex distinction
4 tasks
Collaborator
|
bugbot run |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 50eccb9. Configure here.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relevant issues
Companion to litellm OSS PR #31680 (tag routing negation feature).
Changes
docs/proxy/tag_routing.mdto incorporate existing page content (Quick Start, Calling via Request Header, Setting Default Tags, Team based tag routing) with improved formatting!-prefix tags to exclude deployments by tag, with examples for single provider, multiple providers, fallback chains, and header-based usagetag_regex) section: operator-configured regex matching againstUser-Agent, with config example, verification steps, observability output, and a security caution note clarifying that header-based routing is not a security boundary and requires an upstream auth layerType
📖 Documentation
Note
Low Risk
Documentation-only changes to proxy tag routing; no runtime code or config behavior is modified in this PR.
Overview
docs/proxy/tag_routing.mdis reworked to keep the existing quick start, header tags, default tags, and enterprise team routing, with cleaner Docusaurus-style examples (showLineNumbers,bash/jsonfences) and a shorter quick-start flow.The main new material documents negation (denylist) tags (
!tagin requestmetadata.tagsorx-litellm-tags): how to exclude deployments by exact tag, combine with positive tags, handle ban-only requests, fallbacks, failure modeno_deployments_with_tag_routing, and a semantics table (no regex on client negation tags, untagged deployments never excluded).It also adds/expands
tag_regexoperator routing onUser-Agent, including matching semantics, observability payload, caution that header routing is classification not access control, and how negation runs before regex (with two interaction examples).Reviewed by Cursor Bugbot for commit 50eccb9. Bugbot is set up for automated code reviews on this repo. Configure here.