James Bardin bfa5e7f811 actual value may be unknown in nested list ... When checking AssertObjectCompatible, we need to allow for a possible unkown nested list block, just as we did for a set in 0b2cc62.		2019-06-25 16:43:57 -04:00
..
all_null.go	configs/configschema: Introduce the NestingGroup mode for blocks	2019-04-10 14:53:52 -07:00
compatible.go	actual value may be unknown in nested list	2019-06-25 16:43:57 -04:00
compatible_test.go	actual value may be unknown in nested list	2019-06-25 16:43:57 -04: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
normalize_obj.go	configs/configschema: Introduce the NestingGroup mode for blocks	2019-04-10 14:53:52 -07:00
normalize_obj_test.go	plans/objchange: Don't panic when dynamic-typed attrs are present	2019-03-11 08:18:26 -07:00
objchange.go	configs/configschema: Introduce the NestingGroup mode for blocks	2019-04-10 14:53:52 -07:00
objchange_test.go	don't add empty blocks in ProposedNewObject	2019-03-02 11:21:59 -05:00
plan_valid.go	configs/configschema: Introduce the NestingGroup mode for blocks	2019-04-10 14:53:52 -07:00
plan_valid_test.go	plans/objchange: Don't panic when prior state contains nested map blocks	2019-03-18 09:16:50 -07:00