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

Ability to pass artifacts from CLI #524

jessesuen opened this issue Dec 2, 2017 · 0 comments

Ability to pass artifacts from CLI #524

jessesuen opened this issue Dec 2, 2017 · 0 comments


Copy link

@jessesuen jessesuen commented Dec 2, 2017

In the same manner which we can pass parameters to workflows, users should also be able to pass the location of an artifact as an argument. One use case is for submitting workflows using artifacts from a previous run (e.g. resubmit).

Artifact locations are structured data, so it is not as straightforward as key=value like it is with parameters. But we may be able to handle artifacts which have shorthand URLS and infer the datastructure from the URL. For example:

$ argo submit workflow.yaml -a myart=s3://

$ argo submit workflow.yaml -a myart=

In the S3 case, the URL does not incorporate credentials, so we may need to have to have special logic to somehow fill in the s3 credentials, possibly from the controller configmap.

Alternatively the entire artifact datstructure itself could be specified as json:

$ argo submit workflow.yaml -a myart=json='{"s3":{"bucket":"mybucket","endpoint":"","key":"path/to/art.tgz"}'
@jessesuen jessesuen added this to the M13 milestone Dec 2, 2017
@jessesuen jessesuen removed this from the M13 milestone Jan 11, 2018
@edlee2121 edlee2121 added this to the V2.3 milestone Aug 29, 2018
@alexmt alexmt modified the milestones: v2.3, v2.4 Jan 25, 2019
@jessesuen jessesuen removed this from the v2.4 milestone Apr 19, 2019
@jessesuen jessesuen closed this Apr 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants