You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your enhancement related to a problem? Please describe
As a user I would like to be able to set/override default values of included helm dependencies as defaults in my generated Values.yaml. This can be problematic when that sub chart uses camelCasing. For example when running k8sResource k8sHelm with the gradle plugin, postgres.someValue ends up as postgres.somevalue in the generated Values.yaml file. This is especially problematic because helm best practices suggest camelCasing: https://helm.sh/docs/chart_best_practices/values/#naming-conventions which means most values have this issue.
Describe the solution you'd like
I would like to see the original case provided in Helm.Parameters to be preserved in the generated Values.yaml. To not break anyone who might already have helm parameters with mixed case currently this would be an opt in toggle to preserve case.
Describe alternatives you've considered
#2200 could solve part of the problem as well as long as the case is preserved from the provided Values.yaml file.
Additional context
No response
The text was updated successfully, but these errors were encountered:
In conclusion, I think it's safe to preserve the case-sensitivity and I don't really see the need for adding an additional flag. I'll refactor #2369 accordingly.
Component
JKube Kit
Is your enhancement related to a problem? Please describe
As a user I would like to be able to set/override default values of included helm dependencies as defaults in my generated
Values.yaml
. This can be problematic when that sub chart uses camelCasing. For example when runningk8sResource k8sHelm
with the gradle plugin,postgres.someValue
ends up aspostgres.somevalue
in the generatedValues.yaml
file. This is especially problematic because helm best practices suggest camelCasing: https://helm.sh/docs/chart_best_practices/values/#naming-conventions which means most values have this issue.Describe the solution you'd like
I would like to see the original case provided in Helm.Parameters to be preserved in the generated
Values.yaml
. To not break anyone who might already have helm parameters with mixed case currently this would be an opt in toggle to preserve case.Describe alternatives you've considered
#2200 could solve part of the problem as well as long as the case is preserved from the provided
Values.yaml
file.Additional context
No response
The text was updated successfully, but these errors were encountered: