-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
S3: fix change in behavior in CreateBucketConfiguration #13427
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
Conversation
S3 Image Test Results (AMD64 / ARM64) 2 files 2 suites 8m 10s ⏱️ Results for commit e0f53fc. |
Test Results (amd64) - Integration, Bootstrap 5 files ± 0 5 suites ±0 1h 42m 22s ⏱️ - 59m 11s Results for commit e0f53fc. ± Comparison against base commit 12934db. This pull request removes 3306 tests.♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 1h 20m 20s ⏱️ - 43m 31s Results for commit e0f53fc. ± Comparison against base commit 12934db. This pull request removes 2956 tests. |
k-a-il
left a comment
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.
Nice quick fix, LGTM 👍
Motivation
We got a report that the newer 6.23 Terraform AWS provider version is failing with LocalStack: #13426
This is due to a change in what exceptions are being raised by AWS: previously, if the body contained a
CreateBucketConfigurationXML tag, it also needed to have theLocationConstrainttag inside of it. This seems to have change in AWS, probably related to the new addition of theTagsXML tag inside of it: see https://docs.aws.amazon.com/AmazonS3/latest/API/API_CreateBucket.html#AmazonS3-CreateBucket-request-TagsWhen trying to revalidate the test against AWS, the exception was not raised anymore, so the logic of the provider has been updated.
There is still more to be done to make the
6.23AWS provider work with LocalStack, because it requires the new tagging endpoints that are not yet part of our stubs. Some follow-up work will still need to be done.Changes
CreateBucketConfigurationmust containLocationConstraintanymoreNext up
Support the
Tagsinput value inCreateBucketConfiguration