Conversation
Codex speaks the OpenAI dialect, which the gateway also fronts for
azure_openai-backed MPSes, but the provider-type allowlist only listed
`openai` — so launching Codex against an Azure OpenAI MPS was rejected
("codex can't route to (supported: openai)"). Add azure_openai to codex's
allowed provider types.
Co-authored-by: Isaac <no-reply@databricks.com>
microsoft_foundry speaks the same OpenAI dialect as azure_openai, so add it to codex's provider-type allowlist alongside it. Co-authored-by: Isaac <no-reply@databricks.com>
masonc08
changed the title
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
1 participant
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.
What did you change, and why?
Change: Add
azure_openaiandmicrosoft_foundryto Codex's allowed provider types (_TOOL_PROVIDER_TYPES).Why: Codex speaks the OpenAI dialect, and the AI Gateway fronts
azure_openai- andmicrosoft_foundry-backed Model Provider Services with that same OpenAI surface — but the allowlist only listedopenai, so pointing Codex at one (via--provideror a managed config) failed with "codex can't route to (supported: openai)". This permits both.How do you know it works?
Testing: Extended the provider-support unit test to assert Codex accepts
azure_openaiandmicrosoft_foundry;test_managed_setup.py+test_databricks.pypass (369 tests). End-to-end routing against live Azure OpenAI / Foundry MPSes is being validated separately.This pull request and its description were written by Isaac.