Lists are ordered. If a user changes the order of a list, Terraform will attempt to update the resource. If there are other resources that depend on the list attributes, they'll be destroyed and recreated. That's a big problem for things like CMEK.
A better alternative is to use a set. It's backwards compatible since it's represented the same way in state, but Terraform ignores the order. Terraform automatically sorts set elements alphabetically, so this required updating some test expecteds.
This also means we no longer need to sort regions or other fields according to the plan.
Using the set plan modifiers required pulling in new framework code, so I also took the opportunity to update the framework from 1.3.3 to 1.3.5 for a few minor bug fixes.
Lists are ordered. If a user changes the order of a list, Terraform will attempt to update the resource. If there are other resources that depend on the list attributes, they'll be destroyed and recreated. That's a big problem for things like CMEK.
A better alternative is to use a set. It's backwards compatible since it's represented the same way in state, but Terraform ignores the order. Terraform automatically sorts set elements alphabetically, so this required updating some test expecteds.
This also means we no longer need to sort regions or other fields according to the plan.
Using the set plan modifiers required pulling in new framework code, so I also took the opportunity to update the framework from 1.3.3 to 1.3.5 for a few minor bug fixes.
Commit checklist
make generate
)