-
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
resource/aws_s3_bucket: Add top-level object_lock_enabled
parameter
#23556
Conversation
…_lock_configuration.object_lock_enabled`
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.
Edit: I forgot the aws_s3_bucket_object_lock_configuration
documentation will also need to be updated as the example uses the now-deprecated form, otherwise LGTM 🚀
Good catch on the documentation |
This functionality has been released in v4.5.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. Thank you! |
Starting from AWS provider v4.5.0, an `object_lock_configuration` block in the `aws_s3_bucket` resource is now deprecated and an `object_lock_enabled` attribute inside the `object_lock_configuration` block was moved to a top-level. hashicorp/terraform-provider-aws#23556
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 issues. |
Adds top-level
object_lock_enabled
parameter toaws_s3_bucket
and deprecatesobject_lock_configuration.object_lock_enabled
.Closes #23549
Output from acceptance testing: