Backport of backend/s3: Add wrong bucket region handling to all of S3 client into v1.6 #33906
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
…tantly-genuine-herring
|
Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch. |
alisdair
deleted the
backport/s3/f-add-wrong-s3-region-error/constantly-genuine-herring
branch
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #33885
Uses a middleware handler to return
bucketRegionErrorfor all S3 operations.Works around aws/aws-sdk-go-v2#2282
Target Release
1.6.0
Draft CHANGELOG entry
Not user facing