This message was deleted.

Terraform forces ordering & processing of indexes lexicographically, so in your case, it has to create new indexed list. If

cpu4-mem8

, at position [0], was replaced with

cpu2-mem16

, TF will force the creation of a new index.

Hi @adventurous-battery-36116, thank you for your reply. So their is currently no way to work around this, as this is just how Terraform works?

Yep - it’s a Terraform thing. Re-naming the pools to something like “small”, “medium”, & “large” may help. I ran into a similar issue and worked around it (to a degree) using variable validation: https://github.com/frank-at-suse/vsphere_HA_autoscale_cluster/blob/master/variables.tf