feat: adding the ability to update visibilityTimeout #379
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #370
Description:
As described in the feature request, this PR will add the ability for users to programatically update options for the Consumer. At the moment, this has only been configured with the ability to update
visibilityTimeout
, but in a way that'll be expandable in the future.Type of change:
Why is this change required?:
When an external factor occurs, users may want to trigger an update to the
visibilityTimeout
option that will take effect from that point on.Rather than stopping and then restarting the Consumer, they would like to do this in the current instance.
Code changes:
.updateOption()
, this will take an option and a value and then update the provided option with the provided valueChecklist: