fix(open-webui): wrong behavior on openai api keys #315
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.
Fix #310
This pull request updates the Open WebUI Helm chart to version 8.12.3 and refines the configuration for handling OpenAI API keys and endpoints. The changes clarify and improve how multiple OpenAI API keys are provided and used, especially in deployments with Pipelines enabled, and ensure that environment variables are only set when relevant values are present.
Chart version and documentation updates:
8.12.2to8.12.3inChart.yamland updated the version badge inREADME.mdto reflect the new release. [1] [2]OpenAI API keys configuration improvements:
openaiApiKeysinvalues.yamlfrom a preset list to an empty list, and updated documentation to clarify how keys should be provided, especially when Pipelines are enabled (the list should match the number of URLs, plus one if Pipelines are used). [1] [2]workload-manager.yamlto only set theOPENAI_API_KEYandOPENAI_API_KEYSenvironment variables if the corresponding values are provided, preventing unnecessary or empty environment variables from being set.