add enable
flag for aws_s3_bucket_versioning
#23809
Labels
enhancement
Requests to existing resources that expand the functionality or scope.
service/s3
Issues and PRs that pertain to the s3 service.
stale
Old or inactive issues managed by automation, if no further action taken these will get closed.
Community Note
Description
The
versioning
block of theaws_s3_bucket
resource in the 3.x provider used a booleanenabled
flag. Iffalse
, the bucket would be transparently managed either as unversioned or versioned-suspended as needed to satisfy AWS rules.The new
aws_s3_bucket_versioning
has to be explicitly defined asDisabled
orSuspended
when we don't want versioning enabled. This requires that we now micro-manage individual buckets because some random buckets that were originally created asenabled = false
(unversioned) may have been manually changed to Suspended outside Terraform, say through the S3 console. Those buckets become incompatible with the "Disabled" setting in Terraform. We have a long list of buckets, created by a single module, that we now have to individually parameterize with Disable or Suspended unless we force everything to Suspended.Can a boolean
enable
flag be added toaws_s3_bucket_versioning
that restores the transparent management of unversioned/suspended states?New or Affected Resource(s)
Potential Terraform Configuration
The text was updated successfully, but these errors were encountered: