You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Martin Atkins 0b2cc6298b plans/objchange: Fix panic in AssertObjectCompatible with set blocks ... Our usual "ground rules" for mapping configschema to cty call for the collection values representing nested block types to always be known and non-null, using an empty collection to represent the absense of any blocks of that type so that users can always safely use length(...) etc on them without worrying about them sometimes being null. However, due to some different behaviors in the legacy SDK we've allowed it an exception to this rule which means that we can see unknown and null collections in these positions in object values returned from provider operations like PlanResourceChange and ApplyResourceChange when the legacy SDK opt-out is activated. As a consequence of this, we need to be mindful in our safety check functions, like AssertObjectCompatible here, of tolerating these non-ideal situations to allow the safety checks to complete. We run these checks even when the provider requests an opt-out, because we want to note any inconsistencies as WARNING level log lines to aid in debugging.		7 years ago
..
all_null.go	plans/objchange: Don't presume unknown for values unset in config	7 years ago
compatible.go	plans/objchange: Fix panic in AssertObjectCompatible with set blocks	7 years ago
compatible_test.go	plans/objchange: Fix panic in AssertObjectCompatible with set blocks	7 years ago
doc.go	plans/objchange: logic for merging prior state with config	7 years ago
lcs.go	plans/objchange: LongestCommonSubsequence	7 years ago
lcs_test.go	plans/objchange: LongestCommonSubsequence	7 years ago
objchange.go	core: Restore our EvalReadData behavior	7 years ago
objchange_test.go	plans/objchange: Don't presume unknown for values unset in config	7 years ago
plan_valid.go	plans/objchange: Hide sensitive attribute values in error messages	7 years ago
plan_valid_test.go	plans/objchange: Hide sensitive attribute values in error messages	7 years ago