Default fallback values #503
j-zimnowoda
started this conversation in
General
Replies: 1 comment 1 reply
-
Looking good for starters. I understand that you now see a limitation to use typescript and instead propose go templating for it. However we do have the option to interject the logic step as typescript, i.e. by executing via We can start consolidating the go templating parts we now have and see if we get enough control with it. Otherwise we should use typescript imo. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Default fallback values
Overview
Problems:
Facts about default fallback values:
Values.otomi.adminPassword
Functional requirements:
otomi values
command shall produce values that are composed from user input and default valuesotomi values-defaults
command shall produce all default valuesNon-functional requirements:
helmfile.d/snippets/defaults.yaml
file and removed from other fileshelmfile.d/snippets/env.gotmpl
helmfile.d/snippets/defaults.gotmpl
to retrieve dynamic values (optional needs more investigation to make proper design)Appendix
Methodology for counting all default values
Methodology for counting dynamic default values
Methodology for counting double fallback default values
Beta Was this translation helpful? Give feedback.
All reactions