Repository navigation
chore(llm-routing): reject deprecated multiregion routing aliases at input #1410
Description
Description
Follow-up to #536 (per-model routing configuration). Non-blocking.
Reject the deprecated multiregion routing method spellings at input in the
function API and the CLI, with an error naming the canonical replacements.
Write-time normalization already keeps newly persisted data canonical, so this
is an input-vocabulary cleanup, not a data change. The router keeps read-path
compatibility for pre-existing persisted rows, which are not migrated.
Definition of Done
- API and CLI reject the deprecated multiregion spellings on create and
update with an error naming the canonical names - Existing persisted values keep routing unchanged
- Public docs list only canonical names
Resources
- Parent: feat(llm-routing): support safe, tunable per-model routing configuration #536
- Blocked by: none (can land any time after the parent's control-plane ticket)
Activity
along-2017 commentedon Oct 7, 2026
Closing as not planned. The final design for #536 keeps every routing method spelling, including the deprecated multiregion aliases:
Rejecting the aliases at input would break existing functions and callers for no routing benefit. A one-time conversion of stored names to canonical spellings is only worth doing if the router aliases are ever removed; that would be a new issue.