Add Support for Configuring Secrets for Multiple Model Providers #66
Conversation
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
queryproc
approved these changes
Nov 19, 2024
Member
queryproc
left a comment
queryproc
left a comment
There was a problem hiding this comment.
We should completely remove the use of env vars. There should only exist one way to do this and that should be SECRETS. Let's remove env vars in the next PR.
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.
This pull request add the ability to access secrets required for completing operations and embedding functionalities with Azure and OpenAI services.
If a secret is not found in the internal table, the system automatically falls back to checking the environment variables.