We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
optional
Checklist:
What happened:
Started a step with an input artifact where the bucket does not exist, step failed.
What you expected to happen:
Artifact was marked optional - should pass.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
$ argo version
$ kubectl version -o yaml
Other debugging information (if applicable):
argo --loglevel DEBUG get <workflowname>
kubectl logs <failedpodname> -c init kubectl logs <failedpodname> -c wait
kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)
Logs
argo get <workflowname> kubectl logs <failedpodname> -c init kubectl logs <failedpodname> -c wait kubectl logs -n argo $(kubectl get pods -l app=workflow-controller -n argo -o name)
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
fix: Allow optional input artifacts. Fixes argoproj#2990
dbcc279
fix(executor): Optional input artifacts. Fixes #2990 (#3019)
202d4ab
alexec
Successfully merging a pull request may close this issue.
Checklist:
What happened:
Started a step with an input artifact where the bucket does not exist, step failed.
What you expected to happen:
Artifact was marked optional - should pass.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
Other debugging information (if applicable):
Logs
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: