9 Commits (8423dd4e51a70b7e3249d6d48a8221bbeb4e77ba)

Author	SHA1	Message	Date
Paul Hinze	baa33d7326	core: dag errors should cascade to all descendents ... We weren't marking skipped nodes as failing, so any grandchild-and-deeper dependencies would still evaluate. For example: A -> B -> C -> D If B failed, C would be skipped, but D would still be evaluated. This fixes the behavior so C, D, and any further descendents will all be skipped when B fails. Addresses crashing aspect of #2955 and likely a lot of other confusing failure modes.	11 years ago
Paul Hinze	97acccd3ed	core: targeted operations ... Add `-target=resource` flag to core operations, allowing users to target specific resources in their infrastructure. When `-target` is used, the operation will only apply to that resource and its dependencies. The calculated dependencies are different depending on whether we're running a normal operation or a `terraform destroy`. Generally, "dependencies" refers to ancestors: resources falling _before_ the target in the graph, because their changes are required to accurately act on the target. For destroys, "dependencies" are descendents: those resources which fall _after_ the target. These resources depend on our target, which is going to be destroyed, so they should also be destroyed.	11 years ago
Mitchell Hashimoto	ed2075e384	dag: TransitiveReduction	11 years ago
Mitchell Hashimoto	54fd742ef6	dag: walk should be able to be halted	11 years ago
Mitchell Hashimoto	5b0004ffc7	dag: detect self references, use multierror	11 years ago
Mitchell Hashimoto	e86698c50d	dag: fix walk order issue, scc issues	11 years ago
Mitchell Hashimoto	d59ced3c57	dag: Validate for DAGs	11 years ago
Mitchell Hashimoto	e94c43e0dc	dag: Walk	11 years ago
Mitchell Hashimoto	cfa3d89265	dag: find root of AcyclicGraph	11 years ago