Are there ways to limit the amount of resource checking that happens - other than setting the “check_every” parameter (which TBH seems a bit too simple for many cases) or using webhooks.
What I was thinking of was…
- The current method (check periodically) is fine for resources that have triggers associated - or webhooks.
- For any resources that don’t have triggers or webhooks, automatically check only when the pipeline starts. If the pipeline isn’t running and the resource hasn’t got a trigger, don’t keep checking it.
- for resources that are never ‘got’ only ‘put’, perhaps don’t check them at all (but if they were checked once as per the second point above, that would be OK too).
What do you think? Is that feasible?