fix: r/vsphere_virtual_disk with lazy forces replacement #2033
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1824
Description
Issue addressed - when r/vsphere_virtual_disk.type is set as "lazy" as documented here:
https://registry.terraform.io/providers/hashicorp/vsphere/latest/docs/resources/virtual_disk#type i.e. Thick Provisioned Lazy Zeroed it is sent and received as "preallocated". The value is mapped when sent but not when received which causes disk recreaion when terraform apply is executed for the second time without changing the HCL config.
Fix applied - when virtual disk type is read from the backend the value is transformed to "lazy" if "preallocated" is received.
Testing done:
With HCL:
executed
terraform apply
twiceOutput from the second execution:
Acceptance tests
Output from acceptance testing:
Release Note
Release note for CHANGELOG:
References
#1824