Helm YAML Go text/templates and jwilder/dockerize's docker YAML Go text/templates - which is used by Cadence internally - define the default function with different argument order.
Helm defines it with default-value object argument order.
jwilder/dockerizedefines it with object default-value argument order.
We use both due to mixing Helm level templating and occasionally generating dockerize level templates into the docker configuration file.
I messed the mixing up when I was importing the changes of the new server version.
What's in this PR?
Fixed Cadence mixed Helm, dockerize defaults.
Why?
To correct it.
Additional context
Helm YAML Go text/templates and jwilder/dockerize's docker YAML Go text/templates - which is used by Cadence internally - define the
defaultfunction with different argument order. Helm defines it withdefault-value objectargument order. jwilder/dockerize defines it withobject default-valueargument order.We use both due to mixing Helm level templating and occasionally generating dockerize level templates into the docker configuration file.
I messed the mixing up when I was importing the changes of the new server version.
Checklist
To Do