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
When a workflow contains a daemon task that stops (error/wrong command), Argo no longer interpolates template variables {{steps.my-task.ip}}. While this makes logical sense to not supply an IP Address that does not exist, it does not bubble up the root cause that the daemon is not running.
I would propose instead of not interpolating the variable, argo instead interpolates with the string <daemon-error>
Use Cases
When would you use this?
Debugging issues with daemon tasks/steps
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
When a workflow contains a daemon task that stops (error/wrong command), Argo no longer interpolates template variables
{{steps.my-task.ip}}
. While this makes logical sense to not supply an IP Address that does not exist, it does not bubble up the root cause that the daemon is not running.I would propose instead of not interpolating the variable, argo instead interpolates with the string
<daemon-error>
Use Cases
When would you use this?
Debugging issues with daemon tasks/steps
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: