[X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
Previous versions (< 3.6) of the argo cli just output the error when a workflow submission failed. The current release candidate prints the error, followed by entire the help output. It's a bit tedious to have to scroll back up through all of this each time there's an error. Not sure if this is a bug or a feature request...
Version(s)
v3.6.0-rc3
Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Pre-requisites
:latest
image tag (i.e.quay.io/argoproj/workflow-controller:latest
) and can confirm the issue still exists on:latest
. If not, I have explained why, in detail, in my description below.What happened? What did you expect to happen?
Previous versions (< 3.6) of the argo cli just output the error when a workflow submission failed. The current release candidate prints the error, followed by entire the help output. It's a bit tedious to have to scroll back up through all of this each time there's an error. Not sure if this is a bug or a feature request...
Version(s)
v3.6.0-rc3
Paste a minimal 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