optionally put assets in separate dir #130
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After fetching a release with several artifact files, I want to use a shell script to iterate over those files in a task. Ideally, the shell code would look something like this:
The problem is that these artifacts coexist in the same directory with metadata files
tag
,version
,body
,timestamp
,commit_sha
, andurl
. The*
glob will include those metadata files, but I only want it to include the artifacts downloaded from the GitHub release.So, I propose adding a new boolean source parameter called
asset_dir
. When enabled, the resource will put the artifacts in a new subdirectory calledassets
.I tested my changes with
asset_dir
unset, and the resource downloaded the artifacts to the same directory as the metadata files, preserving the existing behavior. When I tested my changes withasset_dir
set totrue
, the artifacts ended up in a new subdirectory as expected.Thank you for reading my pull-request!