docs: Add postgreSqlInitContainer values to README #648
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
Fixes nextcloud#645 Signed-off-by: Andreas Lindhé <[email protected]>
jessebot
approved these changes
Oct 21, 2024
|
|
Thank you for the quick turn around 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.
Description of the change
This change documents the value field
nextcloud.postgreSqlInitContainer.securityContextin the README.Benefits
The value gets increased visibility to users, so they know it exists.
Possible drawbacks
More docs to maintain.
Applicable issues
nextcloud.postgreSqlInitContainervalue #645Additional information
Manually maintaining such a large table of values seems very tedious and error prone. I would recommend looking into a tool to automate it, for example Bitnami's README generator.
Checklist
Chart.yamlaccording to semver.