-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 #1042
Comments
@rbren yes, I cannot set LLM_API_KEY because we need to setup the token_provider as seen above which in turn requires TENANT_ID, CLIENT_ID, CLIENT_SECRET |
@marcofiocco
OK, but the first part is already there: when litellm is run via opendevin, it already has access to the vars in .env. So if you just create the .env file in opendevin with your settings, litellm should have them.
I don't think so, I think that's what litellm does... You say you tried to integrate it in config.py, but please help me understand here: can you call Azure successfully with this AzureChatOpenAI object or anything else,
|
@enyst
Separately I've tried litellm to setup a key vault:
but |
This parameter, ideally:
|
Directly set AZURE_AD_TOKEN in your env |
Should be fixed by the comment above! |
What problem or use case are you trying to solve?
In my company we have an Azure App sandbox to use OpenAI.
The code we use is:
I have the TENANT_ID, CLIENT_ID, CLIENT_SECRET, but I cannot find any way to use them in OpenDevin.
Describe the UX of the solution you'd like
Allow me to specify them in a
.env
and somehow let me select that backend with a script?Do you have thoughts on the technical implementation?
I've tried to integrate this code https://docs.litellm.ai/docs/secret#azure-key-vault into
config.py
without success. I meanlitellm.get_secret("my-secret-id")
returns empty string. Also I think OpenDevin should be able to callget_secret
regularly because the secret might expire?Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: