You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think what you're describing here is the same as #14048, where data resources were being erroneously shown as being destroyed even though internally they are just removed from the Terraform state.
This was fixed in #15884, which was released in v0.10.4. I believe the output should be correct from v0.10.4 and above.
Since a fix has already been released, I'm going to close this issue. Thanks for reporting this!
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.
ghost
locked and limited conversation to collaborators
Apr 6, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform v0.9.11
terraform plan -destroy
on an EC2 instance mistakenly shows an additional item (subnet) in red whereas the "Plan: " summary shows just a single item.Output from
terraform plan -destroy
:The text was updated successfully, but these errors were encountered: