Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix/AuzreOpenAI embeddings and LLM deployment name #171

Closed
wants to merge 1 commit into from

Conversation

ClaudiaJ
Copy link
Contributor

solves "The API deployment for this resource does not exist" for LLM and embedding models deployed in Azure OpenAI by deployment name supported in tmc/langchaingo#253

We can't Validate OpenAI LLM model names from hard-coded list in Azure because the model name parameter in API request is a deployment name, and while Microsoft advises us to use the model name as deployment name, we did not listen, and I didn't want to coordinate redeploying with a different name on a Friday.

This also permits use of customized models that can be deployed in Azure side-by-side base models as added benefit so I think it was worthwhile.

solves "The API deployment for this resource does not exist" for LLM and
embedding models deployed in Azure OpenAI by deployment name supported
in tmc/langchaingo#253

We can't Validate OpenAI LLM model names from hard-coded list in Azure
because the model name parameter in API request is a deployment name,
and while Microsoft advises us to use the model name as deployment name,
we did not listen, and I didn't want to coordinate redeploying with a
different name on a Friday.

This also permits use of customized models that can be deployed in Azure
side-by-side base models as added benefit so I think it was worthwhile.
@danielchalef
Copy link
Member

@ClaudiaJ This is fantastic. Thank you. I'm aiming to release this with 0.11, likely early next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants