Open ndamclean opened 9 months ago
{{= ... }}
This looks like it could be a whitespace issue. Have you tried removing the space after the =
?
v3.4.3
This is also an older version of Argo and there have been fixes to templating, so I would try a newer version as well.
{{= ... }}
This looks like it could be a whitespace issue. Have you tried removing the space after the
=
?
@agilgur5 I did test removing the whitespace and still saw the same error. Extra whitespace does not make a difference for any other expressions I have tested in Argo.
v3.4.3
This is also an older version of Argo and there have been fixed to templating, so I would try a newer version as well.
I just tried this using v3.4.16
and still saw the same error.
Pre-requisites
:latest
What happened/what did you expect to happen?
When I reference a workflow parameter in an expression
{{= ... }}
the entire expression is not parsed and is treated as a string.For example, the following workflow uses a ternary expression to determine whether to run
true
orfalse
based on a workflow parameter calledsucceed
.I would expect the attached workflow to exit successfully (exit code
0
) ifsucceed
is set totrue
and to fail if it is set tofalse
.However, Argo treats the entire expression as a string without parsing it, resulting in an error message:
If I replace
workflow.parameters['succeed']
with a hard-codedtrue
orfalse
value, the workflow works as expected.Furthermore, if Argo is unable to parse an expression, I would expect
argo submit
orargo lint
to give an error instead of simply treating the unparsed expression as a string. This behaviour makes it very difficult to debug expressions in workflows.Version
v3.4.3
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Logs from the workflow controller
Logs from in your workflow's wait container