terraform/plans/objchange
Martin Atkins 7216049fdb plans/objchange: Improve precision of AssertObjectCompatible with sets
Previously we were just asserting that the number of elements didn't grow
between planned and actual. We still can't precisely correlate elements in
sets with unknown values, but here we adapt some logic we added earlier
to config/hcl2shim to ensure that we can find a plausible correlation for
each element in each set to at least one element in the other set, and
thus catch more cases where set elements might vanish or appear between
plan and apply, for improved safety.

This will still generate false negatives in some cases where unknown
values are present due to having to assume correlation is intended
wherever it is possible, but we'll catch situations where the actual value
is obviously contrary to what was planned.
2019-02-04 18:19:46 -08:00
..
compatible.go plans/objchange: Improve precision of AssertObjectCompatible with sets 2019-02-04 18:19:46 -08:00
compatible_test.go plans/objchange: Improve precision of AssertObjectCompatible with sets 2019-02-04 18:19:46 -08:00
doc.go plans/objchange: logic for merging prior state with config 2018-10-16 19:11:09 -07:00
lcs.go plans/objchange: LongestCommonSubsequence 2018-10-16 19:14:11 -07:00
lcs_test.go plans/objchange: LongestCommonSubsequence 2018-10-16 19:14:11 -07:00
objchange.go more nil/known checks before val.LengthInt 2018-10-19 16:51:15 -04:00
objchange_test.go plans/objchange: Don't panic when a prior value with a set is null 2018-10-17 17:02:47 -07:00