terraform/plans
James Bardin fa8f8df7b6 add ChangesSync.FullDestroy
In order to handle various edge cases during a full destroy, add
FullDestroy to the synchronized changes so we can attempt to deduce if
the plan was created from `terraform destroy`.

It's possible that the plan was created by removing all resourced from
the configuration, but in that case the end result is the same. Any of
the edge cases with provider or destroy provisioner configurations would
not apply, since there would not be any configuration references to
resolve.
2020-10-01 17:08:25 -04:00
..
internal/planproto Regenerate protobuf files under latest versions 2019-09-05 14:36:15 +02:00
objchange Support lists of deeply marked values 2020-09-25 13:33:44 -04:00
planfile finish provider ModuleInstance replacement 2020-03-11 14:19:52 -04:00
action.go Version tools per Go convention under tools.go 2019-10-17 22:23:39 +02:00
action_string.go stringer: Regenerate files with latest version 2019-05-13 15:34:27 +01:00
changes.go Use UnmarkDeepWithPaths and MarkWithPaths 2020-09-10 11:04:17 -04:00
changes_src.go Updates and improvements to comments 2020-09-11 11:15:44 -04:00
changes_state.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
changes_sync.go add ChangesSync.FullDestroy 2020-10-01 17:08:25 -04:00
doc.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
dynamic_value.go Use UnmarkDeepWithPaths and MarkWithPaths 2020-09-10 11:04:17 -04:00
dynamic_value_test.go plans: New package for in-memory plan models 2018-10-16 18:50:29 -07:00
plan.go add state to plans.Plan 2020-09-17 09:54:59 -04:00
plan_test.go finish provider ModuleInstance replacement 2020-03-11 14:19:52 -04:00