fix: consistent variable substitution for configMapKeyRef
. Fixes #13890
#13921
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #13890
Motivation
Support for substituting variables in
configMapKeyRef
was added in #7542 by manually parsing templates out of the string, instead of using the standardtemplate.Replace()
function. Since the manual parsing logic uses the same syntax as simple template tags (e.g.{{workflow.parameters.cm-name}}
), users reasonably expect it to work the same, but it doesn't, which leads to confusion. Additionally, supporting templates like{{workflow.parameters.cm-name}}-cm
is important, because that's a common pattern.Modifications
This replaces the manual parsing code with the standard
template.Replace()
function that everything else uses.Verification
Verified by running the example workflow from #13890 locally: