-
Notifications
You must be signed in to change notification settings - Fork 105
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
Include required properties in --default-values-file-output
#1145
Conversation
Signed-off-by: Praveen Rewar <8457124+praveenrewar@users.noreply.github.com>
375f527
to
f0c4a19
Compare
bc05d42
to
b451598
Compare
-file-output Signed-off-by: Praveen Rewar <8457124+praveenrewar@users.noreply.github.com>
b451598
to
0ad2332
Compare
--default-values-file-output
--default-values-file-output
in package available get Signed-off-by: Praveen Rewar <8457124+praveenrewar@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some thoughts.
Since this PR has a few refactors/improvements separated by commits I was wondering if it would be worth cleaning up some of the nomenclature in default_values.go
The nit mentioned aside I think we should rename the slice of booleans (b
) and even x
(this seems to have different meanings in different scopes?)
k
= key
is the conclusion I drew , but maybe this could have a better name too?
My main concern here is legibility, took me a bit to figure out what b is in context of createDefault
I have done the refactoring in the bash script only and tried to keep the changes in the other files to a minimal. I wanted to do more refactoring in |
I think I am fine with a separate PR for this stuff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
I will be creating a new PR soon. |
What this PR does / why we need it:
Include required properties in --default-values-file-output
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?
Additional Notes for your reviewer:
Review Checklist:
a link to that PR
change
Additional documentation e.g., Proposal, usage docs, etc.: