Martin Atkins 87fe6cbecd plans/objchange: Don't panic when prior state contains nested map blocks ...

We were using the wrong cty operation to access map members, causing a
panic whenever a prior value was present for a resource type with a nested
block backed by a map value.

2019-03-18 09:16:50 -07:00

..

all_null.go

plans/objchange: Don't presume unknown for values unset in config

2019-02-07 14:01:39 -08:00

compatible_test.go

plans/objchange: Fix panic in AssertObjectCompatible with set blocks

2019-02-14 10:04:51 -08:00

compatible.go

plans/objchange: Fix panic in AssertObjectCompatible with set blocks

2019-02-14 10:04:51 -08:00

doc.go

plans/objchange: logic for merging prior state with config

2018-10-16 19:11:09 -07:00

lcs_test.go

plans/objchange: LongestCommonSubsequence

2018-10-16 19:14:11 -07:00

lcs.go

plans/objchange: LongestCommonSubsequence

2018-10-16 19:14:11 -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

normalize_obj.go

plans/objchange: Don't panic when dynamic-typed attrs are present

2019-03-11 08:18:26 -07:00

objchange_test.go

don't add empty blocks in ProposedNewObject

2019-03-02 11:21:59 -05:00

objchange.go

plans/objchange: Don't panic when prior state contains nested map blocks

2019-03-18 09:16:50 -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

plan_valid.go

plans/objchange: Don't panic when prior state contains nested map blocks

2019-03-18 09:16:50 -07:00