Paul Hinze f33ef43195 core: Fix destroy when modules vars are used in resource counts ... A new problem was introduced by the prior fixes for destroy interpolation messages when resources depend on module variables with a _count_ attribute, this makes the variable crucial for properly building the graph - even in destroys. So removing all module variables from the graph as noops was overzealous. By borrowing the logic in `DestroyEdgeInclude` we are able to determine if we need to keep a given module variable relatively easily. I'd like to overhaul the `Destroy: true` implementation so that it does not depend on config at all, but I want to continue for now with the targeted fixes that we can backport into the 0.6 series.		2016-05-18 13:32:49 -05:00
..
child	core: Fix destroy when modules vars are used in resource counts	2016-05-18 13:32:49 -05:00
main.tf	core: Fix destroy when modules vars are used in resource counts	2016-05-18 13:32:49 -05:00