Repository navigation
Maintenance: Mark the Azure AI provider as legacy and point to Custom - #1378
Merged
Merged
Conversation
Backport of the same change made for pre-release (50f15b6, PR #1359). The label has shipped since 7.0.2 (introduced on develop by 281f39ead8, cherry-picked to stable-7.0 as aa2a818162), so the current docs describe a UI that no longer exists: the provider dialog has been offering "Azure AI (legacy deployment-based endpoints)" for the whole 7.0/7.1/7.2 line. The blob of the touched page is identical on main, on pre-release and on the commit the change was written against (db7cbd6), so the port is the same edit with no drift: - Type list entry "Azure AI" -> "Azure AI (legacy deployment-based endpoints)", and "Custom (OpenAI compatible)" -> "Custom (OpenAI Compatible)" to match the dialog label - New paragraph sending Azure admins to Custom with their resource's v1 endpoint, plus the embedding deployment needed for semantic search Claim -> source anchors (zammad, unchanged between 7.2.2 and develop): - ai_provider/azure_ai.coffee:3 (label), :9-11 (model_fields: [], supports_model_listing: false) - ai_provider/custom.coffee:3 (label), :8 (supports_embeddings: true) - lib/ai/provider/azure.rb:78-79 (embeddings raises NotImplementedError), lib/ai/provider.rb:169 in 7.2.x (#supports_embeddings? -> false) - lib/ai/provider/custom_open_ai.rb:39, :73 (appends /chat/completions and /embeddings), :76 (embeddings send model: embedding_model!) The catalog was regenerated on main rather than carried over: its only changes are the strings on this page plus line-number churn.
ArtifactsProduced during runtime |
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
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.
Backport of the same change made for pre-release (50f15b6, PR #1359). The label has shipped since 7.0.2 (introduced on develop by 281f39ead8, cherry-picked to stable-7.0 as aa2a818162), so the current docs describe a UI that no longer exists: the provider dialog has been offering "Azure AI (legacy deployment-based endpoints)" for the whole 7.0/7.1/7.2 line.
The blob of the touched page is identical on main, on pre-release and on the commit the change was written against (db7cbd66), so the port is the same edit with no drift:
Claim -> source anchors (zammad, unchanged between 7.2.2 and develop):
The catalog was regenerated on main rather than carried over: its only changes are the strings on this page plus line-number churn.