fix: Remove Azure OpenAI provider support - #2224
Conversation
This removes Azure OpenAI as a first-class provider across the frontend and backend: settings/onboarding UI, provider model queries, API routes, validation paths, config models, and provider health/registry wiring. It also deletes Azure OpenAI-specific components/helpers and environment/config handling. In parallel, Azure AI Foundry syncing to Langflow was tightened to handle OpenAI-compatible `/openai/v1` endpoints correctly by avoiding dated API version propagation for that endpoint form.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
This removes Azure OpenAI as a first-class provider across the frontend and backend: settings/onboarding UI, provider model queries, API routes, validation paths, config models, and provider health/registry wiring. It also deletes Azure OpenAI-specific components/helpers and environment/config handling.
In parallel, Azure AI Foundry syncing to Langflow was tightened to handle OpenAI-compatible
/openai/v1endpoints correctly by avoiding dated API version propagation for that endpoint form.