[BUG] Rancher don't remember the options defined in the rancher2_machine_config_v2 resource when editing cluster config using the Rancher GUI

Rancher Server Setup

Rancher version: v2.7.9
Installation option (Docker install/Helm Chart): Helm Chart
- RKE2
Proxy/Cert Details: Rancher certificate issued with Let's Encrypt

Information about the Cluster

Kubernetes version: v1.26.11+rke2r1
Cluster Type (Local/Downstream): Downstream
- Infrastructure Provider (VMware vSphere)

User Information

What is the role of the user logged in?
- Admin

Provider Information

What is the version of the Rancher v2 Terraform Provider in use?
- 3.2.0
What is the version of Terraform in use?
- 1.6.6

Describe the bug

After running terraform apply, Rancher don't seem to completely remember the config that was used for provisioning the cluster when using VMware vSphere and viewed in the Rancher GUI. Instead it defaults to the first options available for the fields Data Center, Resource Pool, Datastore and Virtual Machine, and leaves the Folder, and Network fields empty. Leading to cluster changes being done unintentionally when doing stuff from the GUI.

Example of the fields and values specified in the resource rancher2_machine_config_v2:

datacenter    = "SESA"
datastore     = "PRIM-Kub-02"
pool          = "Production IT-1"
network       = [ "Network 606" ]
folder        = "Kubernetes/sesaklulab1
creation_type = "vm"
clone_from    = "kubernetes-template-worker"

To Reproduce

Provision a cluster vith the infrastructure provider VMware vSphere, selecting a different Data Center, Resource Pool, and Datastore fields than the first available.
Wait for the new cluster ro be provisioned.
Login to Rancher GUI and edit the config for the new cluster in the Cluster Manager section.
The Scheduling options should be different than the ones supplied in the rancher2_machine_config_v2 resource

Actual Result

The cluster created with terraform is created, but trying to edit it using the Rancher GUI default to different options then what was specified in the rancher2_machine_config_v2 resource.

Scheduling options changed:

Network options removed:

Virtual Machine changed:

Expected Result

Rancher should remember the options that was defined in the rancher2_machine_config_v2 resource and not default to the first ones available.

rancher / terraform-provider-rancher2