When attempting to override anything using a falsey value in a BB template that handles overrides using a sprig merge or mergeOverwrite, the value will remain unchanged.
For example, attempting to override the flux values for gitlab will only work when overridding using truthy values.
This currently prevents turning off flux features that are defined as true or a positive integer at the top level that need to be disabled on a per app basis.
When attempting to override anything using a falsey value in a BB template that handles overrides using a sprig
merge
ormergeOverwrite
, the value will remain unchanged.For example, attempting to override the flux values for gitlab will only work when overridding using truthy values.
Given the following values
And this line in the current gitlab HelmRelease template
{{- $fluxSettingsGitlab := merge .Values.addons.gitlab.flux .Values.flux -}}
Will result in the following value for
$fluxSettingsGitlab
:since
0
andfalse
are both falsey and5m
is a string which is truthy.The expected result would be
This behavior is not expected to change and is considered a feature in helm
This currently prevents turning off flux features that are defined as
true
or a positive integer at the top level that need to be disabled on a per app basis.