Fix Sqs ErrorType not being parsed properly #3054
Merged
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.
Customer reporting exception error type is not properly handled after the AwsJson-1.0 migration when calling SQS.
For example, when calling
Message does not printed, but instead exception dump does.
This is because Client is listening to an ErrorCode to throw a modelled factory exception. In the above case,
self.client.exceptions.QueueDoesNotExist
ErrorType
should be thrown. However, as a prerequisite of the AwsJson migration, we modified theErrorCode
to ensure a backwards compatibility. In the above case,ErrorCode
should beAWS.SimpleQueueService.NonExistentQueue
.This PR should fix this.