This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
support for passing readme in values yaml #880
Merged
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.
What I Did
Allow app maintainers to override the readme shown in a
helmValues
step.Right now the UI reads this from the
/metadata
endpoint, but now a mantainer can override this.How I Did it
readme.contents
as an optional field tolifecycle.v1.helmValues
readme
is non null on the step, set the values ofdaemontypes.HelmValues.Readme
when returning it down to the frontend.readme
field on the step, otherwise uses areadme
from the chart meta if present.How to verify it
Use a lifecycle like the following, and navigate to helm values step:
Description for the Changelog
Allow app maintainers to override the readme shown in a
helmValues
step.🚢