add a disk on a exists vm will recreate this VM

[johng521888]

Community Guidelines

• I have read and agree to the HashiCorp Community Guidelines .
• Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
• Do not leave "+1" or other comments that do not add relevant information or questions.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

Terraform

1.7.1

Terraform Provider

2.6.1

VMware vSphere

7.0.3

Description

I modified main.tf and tried to add a disk to an existing VM. Terraform apply will recreate my VM, which will cause data loss. Is there any way to avoid the re-creation?

Affected Resources or Data Sources

resource/vsphere_virtual_machine

Terraform Configuration

1、create vsphere vm from template with only one disk first
2、add another disk to the vsphere_virtual_machine resource

Debug Output

vsphere_virtual_machine.vm：Destroying... [id=422de896-1dbe-6669-d019-fa8e69afd15f]

Panic Output

No response

Expected Behavior

when I add a new disk to an existing VM, I want to avoid recreating the VM after executing terraform apply.

Actual Behavior

add new disk will recreate VM

Steps to Reproduce

1、use terraform create an VM with only one disk instance
2、use terraform create an disk
3、Modify the main.tf file of the virtual machine and bind the disk created in the second step to the virtual machine
4、apply this VM will destroy and recreate this VM

Environment Details

No response

Screenshots

No response

References

#434

[github-actions]

Hello, johng521888! 🖐

Thank you for submitting an issue for this provider. The issue will now enter into the issue lifecycle.

If you want to contribute to this project, please review the contributing guidelines and information on submitting pull requests.

[spacegospod]

Hey @johng521888 I tried this myself, I added both a simple disk block and one with a path to an existing vmdk.
Neither of these destroy the VM, they just reconfigure it.
I ran this experiment on a basic VM and on one that I created from a template.

Can you try updating your provider to the latest version?
If you continue to encounter this problem please share your configuration and the output from terraform plan so that we can see the diff