Destroying aws_ecr_replication_configuration resource leaves replication enabled

[sberss]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v0.14.10
+ provider registry.terraform.io/hashicorp/aws v3.36.0

Affected Resource(s)

• aws_ecr_replication_configuration

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

data "aws_caller_identity" "this" {}

resource "aws_ecr_replication_configuration" "this" {
  replication_configuration {
    rule {
      destination {
        region      = "us-east-2"
        registry_id = data.aws_caller_identity.this.account_id
      }   
    }   
  }
}

Debug Output

N/A

Panic Output

N/A

Expected Behavior

When destroying the resource, I expected cross-region replication to be disabled.

Actual Behavior

Cross-region replication was still enabled after destroying the resource (with the same destination regions).

Steps to Reproduce

1. terraform apply
2. terraform destroy

Important Factoids

N/A

References

• ECR cross region image replication #16668

[ghost]

This has been released in version 3.37.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!

[ghost]

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!