terraform/plans
James Bardin ef086399f9 compare empty strings as null in sets
The Legacy SDK cannot handle missing strings from objects in sets, and
will insert an empty string when planning the missing value. This
subverts the `couldHaveUnknownBlockPlaceholder` check, and causes
errors when `dynamic` is used with NestingSet blocks.

We don't have a separate codepath to handle the internals of
AssertObjectCompatible differently for the legacy SDK, but we can treat
empty strings as null strings within set objects to avoid the failed
assertions.
2020-10-19 18:07:45 -04:00
..
internal/planproto Regenerate protobuf files under latest versions 2019-09-05 14:36:15 +02:00
objchange compare empty strings as null in sets 2020-10-19 18:07:45 -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