Misleading reporting of destroyed resources on plan, when forced new resource

[gtmtech]

terraform 0.6.1

Example - change a VPC CIDR block, and plan gives you:

-/+ aws_vpc.default
cidr_block: "10.15.0.0/16" => "10.16.0.0/16" (forces new resource)

but summary gives you:

Plan: 0 to add, 1 to change, 0 to destroy.

This is misleading as your VPC would be destroyed in the process. In general if a resource will end up being destroyed because of a "forces new resource", I should know about it in the plan summary.

[phinze]

Totally agreed with the logic here - this was done in #3173

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