You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change is visible in terraform plan and the disk image is swapped after terraform apply
Actual Behavior
Change is visible in terraform plan and but the disk image on the VM stays identical to the initial configuration. This also results in the fact that re-running terraform apply will keep on indicating that there is a new change.
Steps to Reproduce
Create a VM with an image
Update the image UUID
Apply the modified config
Important Factors
Using Prism Central
References
--->
#0000 <!---Github Issue number --->
The text was updated successfully, but these errors were encountered:
I think customize diff (#173) could not work for us:
I tested it by changing without any luck:
data_source_reference to typelist.
change disk_list to typeSet
removing computed values from disk_list and test.
We can get the change only by adding or removing elements as your current implementation (#157), also I upgraded the provider to the new terraform SDK v1 to see if the behavior is different.
Also, I got from Hashicorp: customizediff is sort of actively discouraged, despite not having a replacement
Let the user know about updating the data_source reference is not possible by Terraform and should use terraform taint to force the VM recreation. https://www.terraform.io/docs/commands/taint.html
Nutanix Cluster Information
Terraform Version
Terraform v0.12.24
Affected Resource(s)
Terraform Configuration Files
Create VM with a disk that references an image:
Change the image id and apply:
Debug Output
None
Panic Output
None
Expected Behavior
Change is visible in
terraform plan
and the disk image is swapped afterterraform apply
Actual Behavior
Change is visible in
terraform plan
and but the disk image on the VM stays identical to the initial configuration. This also results in the fact that re-runningterraform apply
will keep on indicating that there is a new change.Steps to Reproduce
Important Factors
Using Prism Central
References
--->
The text was updated successfully, but these errors were encountered: