ignore_changes still says it plans to destroy even though it doesn't

[ahodges22]

Follow up from #3555

I'm running the latest version of Terraform (v0.6.16), and when managing AWS instances and setting it to ignore AMI changes with this:

  lifecycle {
        ignore_changes = ["ami"]
    }

I still have it telling me it's planning on destroying my instances when I update the AMI ID to something new:

Plan: 0 to add, 3 to change, 5 to destroy.

I created a test instance to see if it would actually destroy the instance, and it doesn't. However I'd like to have it not say # to destroy on Terraform Plan if it is not actually planning on destroying these instances.

[ahodges22]

Duplicate: #6379

[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 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.