-
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
Support for optional input artifacts #805
Comments
In other words, are you asking for default field for artifacts? I think it is possible for artifacts to follow the same semantics as parameters. If there is a default value for an input artifact, then it becomes optional. |
I was hoping for some way to say that a file was intentionally not supplied, so the container can detect it's missing and react accordingly (e.g. a shell script could omit an optional argument to a tool). |
FEATURE REQUEST:
In order to support building workflows out of reusable templates, I'd like to see Argo support optional input artifacts. At the moment, failing to provide an input artifact when a step calls a template is always an error. Parameters are already optional if they have a default value.
Has this been considered?
The text was updated successfully, but these errors were encountered: