Closed xtiannano closed 2 years ago
Hey @xtiannano 👋 Thank you for taking the time to raise this. So that we have all of the information we need in order to look into this, can you update the issue description to include the Terraform configuration itself (in addition to the diff that you already included -- thanks for that!) so that we can see how you're defining the resource(s)?
@justinretzolk thanks for taking the initiative to start triaging this and after careful checking on the rules, it was just due to a duplicate rule below that was causing the diff on the plan and after removing the duplicate, It doesn't detect anymore changes. Apologies for raising this and I shall go ahead and close this issue `- excluded_rule {
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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Terraform CLI and Terraform AWS Provider Version
Terraform v0.13.7 tried it both on aws v3.58.0 and aws v3.73.0 but still issue persists.
Affected Resource(s)
aws_wafv2_web_acl
Terraform Configuration Files
Expected Behavior
After applying it initially, a plan shouldn't be provided
Actual Behavior
After applying, a plan is provided to destroy and create the same rules again
Steps to Reproduce
terraform apply