Support API key in config for LiteLLM #1747
Closed
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.
Added support for specifying the API key via the configuration object (
self.config.api_key
) instead of relying solely on environment variables. This change provides more flexibility in managing API keys.Description
This update adds the ability to set the API key directly in the configuration object (
self.config.api_key
), instead of being limited to using environment variables. This enhancement offers more flexibility for developers by allowing API keys to be managed within their application's configuration files. This change is especially beneficial for those who prefer or require configuration-based management for sensitive information.Fixes #1746
Type of change
How Has This Been Tested?
The changes were tested by updating the configuration object to include the API key (
self.config.api_key
) and verifying that the application correctly uses this key for API calls.Checklist:
Maintainer Checklist