-
Notifications
You must be signed in to change notification settings - Fork 9.2k
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
New Resource: aws_s3control_bucket_policy #15416
Comments
* New Resource: aws_s3control_bucket_policy Reference: #15412 Reference: #15416 Output from acceptance testing: ``` Pending ``` * tests/resource/aws_s3control_bucket_policy: Fixes since Public Access Block is always enabled for S3 Control Buckets Output from acceptance testing: ``` --- PASS: TestAccAWSS3ControlBucketPolicy_disappears (32.85s) --- PASS: TestAccAWSS3ControlBucketPolicy_Policy (43.13s) --- PASS: TestAccAWSS3ControlBucketPolicy_basic (106.91s) ``` * resource/aws_s3control_bucket_policy: terrafmt fixes * Update aws/resource_aws_s3control_bucket_policy_test.go
Support for this new resource has been merged and will release with version 3.13.0 of the Terraform AWS Provider, later this week. 👍 |
This has been released in version 3.13.0 of the Terraform AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template for triage. Thanks! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Community Note
Description
As part of the initial S3 on Outposts support for the Terraform AWS Provider, a new resource for managing Bucket Policies in the S3 Control API is necessary. This new resource does not deprecate the existing
aws_s3_bucket
/aws_s3_bucket_policy
resource functionality and does not represent any operator need for migration between the two. Resource documentation call out boxes will be in place to help delineate the purpose of the two similar, but different resources.New Resource
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: