mirror of
https://github.com/Nezumi-2711/9router.git
synced 2026-09-22 20:00:47 +00:00
commit 8b2ab7c9e05689c1bf55002cc79db8d22a398c75 Author: kundeng <kundeng@live.com> Date: Mon Apr 20 11:26:58 2026 -0400 fix: send providerSpecificData in Edit modal validate calls The Check button in the Edit modal was sending only apiKey without the Azure endpoint/deployment/org, causing validation to fail. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> commit c894fa838d035ecd9a160339342371042697c327 Author: kundeng <kundeng@live.com> Date: Mon Apr 20 01:45:13 2026 -0400 fix: persist Azure providerSpecificData and add connection test - Read body.providerSpecificData in POST /api/providers so Azure fields (endpoint, deployment, apiVersion, organization) are actually stored - Add azure case to testApiKeyConnection so the Test button works correctly instead of falling through to "not supported" Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> commit 00bd1a4151f4e73616969e25d1786c87d1ec0d5e Author: kundeng <kundeng@live.com> Date: Mon Apr 20 01:24:39 2026 -0400 fix: add Azure validation and make Organization required - Add Azure case to /api/providers/validate that sends a test chat completion with api-key header and organization - Pass Azure-specific data (endpoint, deployment, apiVersion, org) from Add modal to validate endpoint - Make Organization field required (needed for billing) Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> commit a66a04daab69b07baa4cc6b28772249e4b25ea19 Author: kundeng <kundeng@live.com> Date: Mon Apr 20 01:15:53 2026 -0400 fix: add Azure config fields to Add API Key modal The Add modal was missing the Azure-specific fields (endpoint, deployment, API version, organization) — only the Edit modal had them. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> commit 6ac3f4a97af8468d210594495ce754f5d7a7978a Author: kundeng <kundeng@live.com> Date: Mon Apr 20 01:06:45 2026 -0400 feat: add Azure OpenAI as a dedicated provider Azure OpenAI uses a different URL scheme (deployments-based) and api-key header auth instead of Bearer tokens. This adds a dedicated AzureExecutor that constructs the correct URL and headers, plus dashboard UI fields for endpoint, deployment, API version, and organization. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>