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

Detect inputs to a put step #2692

clarafu opened this issue Oct 16, 2018 · 0 comments · Fixed by #4616

Detect inputs to a put step #2692

clarafu opened this issue Oct 16, 2018 · 0 comments · Fixed by #4616


Copy link

@clarafu clarafu commented Oct 16, 2018

With #1202 implemented, it is sort of redundant to need to type out all the artifact inputs to a put step while they "most likely" have already written out the artifacts that are needed in the params. The only case we can think of for now that would not have the artifacts specified in the put params is when you would use a wildcard, which is covered by the "all" option for the inputs to a put configuration.

We can add a "detect" option to the input configuration for a put step that will go through the params and grab out a list of all the artifacts that were specified within it and use those as the inputs. It might look something like this:

- get: some-repo
- put: some-resource
  inputs: detect
    doesnt_matter: some-repo/hello

In this example we would take the some-repo from some-repo/hello and deduce that some-repo is an artifact to pull in as an input. This won't always correspond to an artifact, and in that case it should just be skipped. Note that the value some-repo should also be used to look up an artifact.

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.

2 participants