-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
S3Control: implement Tagging support for S3 Bucket #13435
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
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 36s ⏱️ - 2h 2m 7s Results for commit 7374569. ± Comparison against base commit 9e9f65f. This pull request removes 4963 and adds 3 tests. Note that renamed tests count towards both. |
Test Results (amd64) - Integration, Bootstrap 5 files ± 0 5 suites ±0 9m 1s ⏱️ - 2h 34m 1s Results for commit 7374569. ± Comparison against base commit 9e9f65f. This pull request removes 5313 and adds 3 tests. Note that renamed tests count towards both. |
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.
Great to see this parity gap to be fixed. I tested S3Control locally, and it works as expected 🚀
Motivation
Following the #13426 report and fixing the first reported issue, when trying the sample, I got a report from Terraform than the tagging operations for S3 were not implemented, but after having a better look I finally realized it was S3 Control:
I first got this issue:
Because the
skip_requesting_account_id = truewas set, but worked after removing it, so something to keep note of.This PR implements implements the 3 tagging operations
ListTagsForResource,TagResourceandUntagResourcefor S3 Buckets via S3 Control.This unblocks the
6.23AWS Terraform provider and it now works if you check out this PR.A follow up from this pr will be to implement
PutBucketAbacandGetBucketAbac.Another thing to note is that S3 Control is heavily tied and coupled to S3, and seems to be able to mutate S3 internal state in AWS without going through public APIs, which justify the uses of the
s3_storesdirectly here.Changes
Tests
To fully validate that the issue is fixed for the Terraform provider, you can try the sample given in the linked issue, just remove the
skip_requesting_account_id = trueline.