Proposing the simple, open, concourse-webhook-resources which

[ardavanhashemzadeh]

may be used to fly pipelines using API calls.

[bgandon]

Just saying, but:

1. There is also no need to store the whole log of all passed triggers timestamps, because only the last timestamp is enough, since you're basically implementing a “black out” window of X seconds (X configured in source.limit) during which no trigger will generate any new version.
2. There is no need for a Git backend to store the timestamp of the last trigger. Indeed, the storage trick used by the gstack/keyval-resource would be enough to store the last trigger timestamp and implement the “black out” window.

Maybe you should detail more your use-case requiring a Git repo as storage backend, or just implement a more lightweight approach.

The name “webook-resource” is surprising either. In fact, you don't implement any webhook endpoint, as you just benefit from the default one provided by Concourse. Your resource only brings a throttling feature. Thus I would suggest you call it the “throttling-resource”.

[ardavanhashemzadeh]

Thanks for the feedback, git may be heavy handed if Concourse is already saving history. I'll cut the cruft and name it more appropriately.

[bgandon]

Always happy to welcome new resource authors.

Well, it's no more heavy since the timestamp is already stored in the version history of the resource, and that's precisely the trick of the keyval-resource.

I would also suggest you document your resource, looking at other popular resources like “git-resource” or “registry-image” and set up a README.md that looks similar.