When there is a Deployment with resource configurations for VMs that contain more or different custom properties within theconfiguration map, each time whenterraform plan is run, there is a diff produced that completely removes theconfiguration block withinresource_configuration and adds a new one with only the values provided in thevra7_deployment TF resource.

This seems to be becauseresource_configuration is aTypeSet in the Resource Schema.

That means, each time the hash calculated from the settings in the state is not identical to the one in the resource config, Terraform treats it as a differentresource_configuration and wants to remove the existing block from the state and put in only the values in the config.

For this, I propose to change this toTypeList. However, this would depend on the vRA7 API returning thecontent[] in theResourceView response always in the same order (which I'm not 100 % sure of right now).

After changing the Type to List, we also add aDiffSuppressFunc to theconfiguration Element that checks if a custom property from the state needs to be included in the diff.

If it set in the state, but NOT in the resource config, we ignore the diff. This is because often there are quite a lot of custom properties returned for a VM that are set on vRA side and are not of interest to the resource configuration in the first place.

Aims tofix#56