Add S3ResponseError.operation_name #530
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
waahm7
approved these changes
Nov 22, 2023
graebm
force-pushed
the
s3-operation-name
branch
from
fd40563 to
100aa40
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This hooks up functionality from:
awslabs/aws-c-s3#377
Issue:
If an AWS SDK is using the CRT S3 client, it was difficult to map CRT exceptions to SDK exceptions since it wasn't clear exactly which S3 HTTP request failed (A CRT S3 request might make several HTTP requests under the hood)
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.