Changes to Bucket Versioning Configuration outside of terraform not detected.

[mviamari]

When the Versioning configuration (Enabled/Suspended) is changed outside of Terraform, the change is not detected by the module and the configuration persists on the bucket, even when the module has versioning disabled.

It seems that this is because the module enables versioning by adding/removing the aws_s3_bucket_versioning resource, instead of changing the aws_s3_bucket_versioning.versioning_configuration.status from Enabled to Suspended. This seems correct according to the docs, which note that deleting the resource will set the versioning to suspended. However, without the aws_s3_bucket_versioning resource changes made external to the terraform do not appear to be detected/corrected.

Expected Behavior

If the versioning configuration is changed outside of terraform, the change is detected and a diff is generated to match the configuration to the terraform.

Steps to Reproduce

1. Deploy S3 bucket with versioning_enabled=False
2. Change the versioning to enabled the Console (or at least outside of the terraform configuration).
3. Re-run terraform to see if the change is detected.

Environment

Terraform v1.2.8
AWS provider v4.50.0
Cloudposse s3_bucket module 3.0.0