Paul Hinze 64f0897c82 core: avoid diff mismatch on NewRemoved fields during -/+ ... fixes #1508 In a DESTROY/CREATE scenario, the plan diff will be run against the state of the old instance, while the apply diff will be run against an empty state (because the state is cleared when the destroy node does its thing.) For complex attributes, this can result in keys that seem to disappear between the two diffs, when in reality everything is working just fine. Same() needs to take into account this scenario by analyzing NewRemoved and treating as "Same" a diff that does indeed have that key removed.		2015-04-14 17:23:30 -05:00
..
bins	Merge pull request #1185 from hashicorp/f-remote-resource	2015-04-01 22:50:30 -07:00
providers	core: avoid diff mismatch on NewRemoved fields during -/+	2015-04-14 17:23:30 -05:00
provisioners	Add cleanup function to close SSHAgent	2015-03-20 18:18:35 -07:00