Martin Atkins a1a713cf28 core: Report ActionReasons when we plan to delete "orphans" ... There are a few different reasons why a resource instance tracked in the prior state might be considered an "orphan", but previously we reported them all identically in the planned changes. In order to help users understand the reason for a surprising planned delete, we'll now try to specify an additional reason for the planned deletion, covering all of the main reasons why that could happen. This commit only introduces the new detail to the plans.Changes result, though it also incidentally exposes it as part of the JSON plan result in order to keep that working without returning errors in these new cases. We'll expose this information in the human-oriented UI output in a subsequent commit.		2021-09-23 14:37:08 -07:00
..
doc.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00
module.go	Move command/ to internal/command/	2021-05-17 14:09:07 -07:00
plan.go	core: Report ActionReasons when we plan to delete "orphans"	2021-09-23 14:37:08 -07:00
plan_test.go	jsonplan and jsonstate: include sensitive_values in state representations (#28889)	2021-06-14 09:19:13 -04:00
resource.go	json-output: Previous address for resource changes	2021-09-20 15:25:23 -04:00
values.go	de-linting	2021-09-01 11:36:21 -04:00
values_test.go	jsonplan and jsonstate: include sensitive_values in state representations (#28889)	2021-06-14 09:19:13 -04:00