-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error submitting workflow via argo cli when passing --parameter-file flag #8160
Labels
Comments
@asaunders57 Can you try without argo server? looks like the file is not able in your current folder/doesn't have permission to open it. |
There is a bug here that could have been a security issue. When submitting via the server, the parameter file is read, but is read from the server file-system. Luckily |
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Mar 22, 2022
…oproj#8160 Signed-off-by: Alex Collins <alex_collins@intuit.com>
alexec
added a commit
to alexec/argo-workflows
that referenced
this issue
Mar 22, 2022
…oproj#8160 Signed-off-by: Alex Collins <alex_collins@intuit.com>
dpadhiar
pushed a commit
to dpadhiar/argo-workflows
that referenced
this issue
Mar 23, 2022
…rgoproj#8160 (argoproj#8213) Signed-off-by: Alex Collins <alex_collins@intuit.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Summary
What happened/what you expected to happen?
Connected to the Argo server API by setting the environment variables found in the User Info section of the Argo Workflows UI.
Attempted to submit a Workflow from an existing WorkflowTemplate:
argo --loglevel debug submit --from wftmpl/deployment-workflow-template -n argo --parameter-file deploy-config.yaml
Logs below showing evidence of:
--parameter-file
flagI've omitted the server URL and port.
argo-workflows-server log entry:
The commands above are executed in a GitLab runner container. When I run the same command locally - connecting via the k8s API server with no ARGO env vars set, it succeeds.
The deploy-config.yaml exists and the file permissions are fine, so I am unsure as to the origin of the error. Further, it's odd that this does not occur in the case mentioned above.
What version are you running?
v3.3.0, this behaviour also occurs in v3.2.9
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: