-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update AWS SDK versions to the latest #34796
Conversation
I've notified the teams responsible for triaging S3 backend related issues. Thanks for this submission. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thanks, @kojoru
Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch. |
#34528 occurs for us frequently in or ci/cd process on our self-hosted runners in aws. It occurs most frequently when there are no changes to the plan but the state is being updated anyway. It also occurs quite frequently when there are many quick updates to the s3 bucket for very fast operations on items that do not take much time to deploy. It has never occured for me when we run locally only on our cicd runners hosted in aws. |
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. |
This pull request updates the AWS SDKs to the latest version.
The intent is to fix #34528, which is intermittent and can't be easily reproduced.
The root cause was discussed in the relevant AWS SDK issue and AWS folks couldn't reproduce this situation on the latest versions of their SDK.
Hence, this pull request.
Target Release
1.7.x, 1.8.x
Draft CHANGELOG entry
BUG FIXES