terraform/plans
James Bardin f128b8c4fa take dynamic types into account when comparing set
If a NestingList or NestingMap contains a dynamic type, they must be
handled as a cty.Tuple and cty.Object respectively, because the elements
may not have precisely matching types.
2020-10-15 20:07:00 -04:00
..
internal/planproto Regenerate protobuf files under latest versions 2019-09-05 14:36:15 +02:00
objchange take dynamic types into account when comparing set 2020-10-15 20:07:00 -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 rely solely on the plan changes for outputs 2020-10-12 18:59:14 -04:00
changes_src.go Updates and improvements to comments 2020-09-11 11:15:44 -04:00
changes_state.go
changes_sync.go s/FullDestroy/IsFullDdestroy/ 2020-10-05 10:50:25 -04:00
doc.go
dynamic_value.go Use UnmarkDeepWithPaths and MarkWithPaths 2020-09-10 11:04:17 -04:00
dynamic_value_test.go
plan.go add state to plans.Plan 2020-09-17 09:54:59 -04:00
plan_test.go remove LegacyProvider (#26433) 2020-10-05 08:33:49 -04:00