-
-
Notifications
You must be signed in to change notification settings - Fork 588
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Standardise Values.yaml structure #164
Comments
In addition to #177 this issue also entails verifying the references in each chart.yaml file, such as sources. |
Charts.yaml should be done by now, but at least the standardised formatting is created and applied to current Apps |
Values.yaml also need to be split into:
As those are breaking changes, i'm going to put this Issue on the "Next SCALE release" project. |
Fixed on staging branch! |
This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists |
Is your feature request related to a problem? Please describe.
Currently the order of settings in Charts.yaml and values.yaml files is all-over-the place.
This consequence of this, is it being increasingly hard to execute bulk-edits for those files.
Which are often required when doing big, multi-chart updates such as questions.yaml updates.
Describe the solution you'd like
All of these files have a rather simple structure and are easily restructured.
Restructuring them and making sure they all have the same order of settings, is a solid solution to ensure easy bulk-updating of charts.
Describe alternatives you've considered
Leaving it up to the app maintainers.
However: Bulk edits often have to be done by others than the app maintainers, so that wouldn't actually solve anything
The text was updated successfully, but these errors were encountered: