-
Notifications
You must be signed in to change notification settings - Fork 98
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
Azure OpenAI auth - not possible to specify api-key
for (default)embedding-model
#1154
Labels
Comments
Thanks for reporting. The same issue exists for the chat model too, right? |
Yes! |
@edeandrea WDYT? |
Sounds reasonable. If you're looking for me to take this up I don't think I'm going to have the bandwidth for a bit. |
👍🏽 |
@flyinfish would you be interested in contributing this? |
Can give a shot |
👌 |
flyinfish
pushed a commit
to flyinfish/quarkus-langchain4j
that referenced
this issue
Dec 20, 2024
for chat-, embedding-, and image-model: api-key, ad-token, api-version Closes quarkiverse#1154
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BUG
when using an embedding model it is possible to specify a dedicated endpoint, but not a dedicated api-key
when using ad different
resource-name
as inquarkus.langchain4j.azure-openai
there will be a differentapi-key
needed as well. but forapi-key
it falls back toquarkus.langchain4j.azure-openai
or refusing to start if not present:Expected Behaviour
should be possible to specify
Workaround
the workaround for some cases might be using a
@ModelName
this works as expectedReproduce
<quarkus-langchain4j.version>0.22.0</quarkus-langchain4j.version>
https://github.com/flyinfish/quarkus-langchain4j--samples-azure-openai/tree/use-separate-resource-name/chatbot
https://github.com/flyinfish/quarkus-langchain4j--samples-azure-openai/blob/use-separate-resource-name/chatbot/.env-template
The text was updated successfully, but these errors were encountered: