Allow configurable update interval and backoff

[vililahtevanoja-solibri]

In #28 an issue was encountered with exceeding API rate limits. This was attended to with PR #29 where the update query interval was increased to 30s, and handling was added for rate exceeded error.

30s interval also has the effect of adding a 0-30s overhead to each action, depending on when the CodeBuild job happens to complete. For some use cases this overhead can be quite noticeable and unnecessary. E.g. for a singular/small group of short CodeBuild build(s), where we have little danger of hitting the rate-limiting. Some use-cases may also involve running CodeBuild builds in sequence, where this overhead is multiplied by the number of sequenced builds.

Offering a way to configure the update interval and backoff, rather than have them hard-coded as they are now, allows for a more fine-grained way to tune the API call rate to fit the use-case. This makes it possible to limit the unnecessary time overhead involved and enable a faster turn-around time. The current values could be kept as default.

[DrewCurd]

Is there anymore news on this one if configurable interval and backoff is in the future?

[vililahtevanoja]

Is there anymore news on this one if configurable interval and backoff is in the future?

The CI run for #76 was approved after I had already moved on from a client, so I didn't see what happened with the CI run and do not have access to that account anymore. Apparently there was some error in the run but alas those logs are long lost now. The codebase has seen very few changes so I created #77 with the same changes on top of the current master-branch here. Hoping that it will chug along a bit more swimmingly 🤞🏻

[vililahtevanoja]

This can be closed, as the implementation was merged in #116 and released with v1.0.8.