fix #5614: Fixed the template error null pointer evaluation #5615
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 latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hi @Pit-Storm , curious do you use LiteLLM today ? If so, I'd love to hop on a call and learn how we can improve LiteLLM for you
|
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.
Title
The null pointer evaluation was fixed by introducing the new default variable
values.db.urlwith a default value using dependent variables. Also with this approach you can overwrite the default value and don't need a function helper to evaluate if this value is set. Also added it to the readme.Relevant issues
Fixes #5614
Type
🐛 Bug Fix
Changes
in files:
deployment.yaml
values.yaml
README.md