Handle expected boolean values for waiter error matcher #8804
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.
Summary
All services currently define waiter error acceptors that have
expected
string values that represent an AWS Error code like below:A waiter with this acceptor will continue to wait until an error the the code
ResourceNotFoundFault
is received or the max amount of attempts is reached.However, it's possible for service teams to define a waiter error acceptor like below which has an
expected
boolean (true
orfalse
) value. The expected behavior is defined below:true
- Match an error code with any value.false
- Match if no errors were encounteredExample:
A waiter with this acceptor will continue to wait until a response with no error is received or the max amount of attempts is reached.
This CR adds the ability for waiters to handle the acceptors described above.