Skip to content
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

Closed
mthx opened this issue Mar 24, 2018 · 3 comments
Closed

Support for optional input artifacts #805

mthx opened this issue Mar 24, 2018 · 3 comments

Comments

@mthx
Copy link
Contributor

@mthx mthx commented Mar 24, 2018

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?

@jessesuen
Copy link
Contributor

@jessesuen jessesuen commented Apr 2, 2018

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.

@mthx
Copy link
Contributor Author

@mthx mthx commented Apr 27, 2018

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).

@jessesuen jessesuen closed this Apr 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants