📝 Deprecate skip_download
in favour of no_get
#10
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.
skip_download: true
allows us to prevent re-downloading in the implicit get step that is run after a put step. However, this has the added drawback of leaving us with an empty volume which means we need to alias the resource for updating the pull-request.We can instead use
no_get: true
on the put step to prevent the get step from running entirely, removing the need to alias the resource as the volume will be un-affected.https://concourse-ci.org/put-step.html#schema.put.no_get