Move api_key from additional kwargs to OpenAI instantiation #500
Conversation
This file contains 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
The openai api config key is caused issue for azure openai, when passed in additional kwargs to litellm completion. Instead it is passed as arg to OpenAI instantiation.
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.
When the api_key is passed in additional kwargs to the litellm completion, it caused an issue with Azure OpenAI.
To fix it, it is passed as an arg to the OpenAI instantiation, and removed from additional kwargs in the handler.
I don't know if this might cause issues for other LiteLLM backends though.
But if it does, it probably indicates that a refactor is needed in order handle multiple backends