No trigger on empty s3-resource

#1

Hello there,

The resource (https://github.com/concourse/s3-resource) triggers a job even when the corresponding file does not exist (on s3). This is default behavior and can be further defined with the initial_version option (versioned).

However I do NOT want to trigger if the file does not exist. So is that something that can be disabled with a parameter?

Thanks!

0 Likes

#2

This is good idea that you could put as an issue in that repo: https://github.com/concourse/s3-resource/issues

From the interface perspective (see here) this looks like it should be possible.

0 Likes