-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
r/aws_s3_bucket_object: Add support for S3 Object Lock legal holds #7158
Comments
Suggested syntax: resource "aws_s3_bucket_object" "foo" {
bucket = "my-versioning-bucket"
key = "important-data.txt"
legal_hold {
status = "ON"
}
} |
With the new PR I am going with a simplified syntax that is more in line with the S3 API: resource "aws_s3_bucket_object" "example" {
object_lock_legal_hold_status = "ON"
} |
The enhancement to the |
This has been released in version 2.29.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
Now that S3 buckets support Amazon S3 Object Lock (#6634 & #6872), add support for S3 object legal holds to the
aws_s3_bucket_object
resource and data source.The text was updated successfully, but these errors were encountered: