terraform/plans/objchange
Kristin Laemmert c661157999 plans/objchange: further harden ProposedNewObject against ~weird~
incoming values

Addresses an odd state where the priorV of an object to be changed is
known but null.

While this situation should not happen, it seemed prudent to ensure that
core is resilient to providers sending incorrect values (which might
also occur with manually edited state).
2018-10-16 19:14:11 -07:00
..
compatible.go plans/objchange: Fix handling of unknown in AssertValueCompatible 2018-10-16 19:14:11 -07:00
compatible_test.go plans/objchange: AssertObjectSuperset function 2018-10-16 19:11:09 -07:00
doc.go
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 plans/objchange: further harden ProposedNewObject against ~weird~ 2018-10-16 19:14:11 -07:00
objchange_test.go plans/objchange: when prior is null, computed attributes are unknown 2018-10-16 19:14:11 -07:00