fix(proxy): add coordination_redis routes to component allowlist - #32805
Conversation
Greptile SummaryThis PR adds
Confidence Score: 5/5Safe to merge; the change is a one-line addition to a static allowlist tuple with no runtime logic involved. The change is a single entry added to a read-only tuple. The affected test passes according to the provided output, the prefix No files require special attention.
|
| Filename | Overview |
|---|---|
| backend/routes/allowlist.py | Added /coordination_redis/ prefix to BACKEND_PATH_PREFIXES, covering the two routes introduced by PR #32661 (/coordination_redis/settings and /coordination_redis/settings/test) |
Reviews (1): Last reviewed commit: "fix(proxy): add coordination_redis route..." | Re-trigger Greptile
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
7170c01
into
litellm_coordination_redis_config
Relevant issues
Unblocks PR #32661.
Linear ticket
Resolves LIT-3861
Pre-Submission checklist
Screenshots / Proof of Fix
Type
🐛 Bug Fix
Changes
PR #32661 added
/coordination_redis/settingsand/coordination_redis/settings/testendpoints but did not add them tobackend/routes/allowlist.py. Thetest_gateway_plus_backend_covers_full_apptest enforces that every registered route appears in either the gateway or backend allowlist, causing that test to fail with:Adding
/coordination_redis/as a prefix entry to the backend allowlist covers both routes and unblocks the CI check