Skip to content

Is the implicit get after a put necessary? #32

@pn-santos

Description

@pn-santos

Is the implicit get that concourse does after a put is necessary for this resource to work? or could it be skipped?

I've had a look at the source code and there seems to be no way to use something similar to the get_params: {skip_download: true} of the docker image resource to skip the implicit get step (please correct me if I'm wrong).

In my case, I'm running 4 "checks" concurrently and at first glance, the get that is always executed after I update the checks status (with put) seems unecessary... Would it make sense to check for a "skip" in the in step?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions