Properly handle JSON server config #1049
Merged
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
benashz
deleted the
VAULT-25346/fix-properly-handle-json-encoded-server-config
branch
|
Thanks! |
This was referenced Nov 6, 2024
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.
The changes made to generate the server configuration in d186b6f broke the user's ability to provide extra server configuration as JSON. This PR adds checks to ensure that the extra server configuration can be specified as JSON.
The same change mentioned above introduced support for setting the extra server configuration from a YAML structure, unfortunately Helm is not able to properly render the value given the defaults found in
values.yaml. This PR enforces that config value must be a string.