terraform updating bootdisk in place when no changes are made

[hestiahacker]

When I deploy a VM using terraform apply, and then immediately try to terraform apply again, the provider tells me that the the bootdisk is being added. It will tell me this every single time I run terraform apply. Here's what it looks like:

  # module.foobar.module.vm.module.vm.proxmox_vm_qemu.server will be updated in-place
  ~ resource "proxmox_vm_qemu" "server" {
      + bootdisk               = "virtio0"

This has been confirmed on 3.0.1-rc6, but I can't remember when it first started showing up.

This isn't a huge deal for me personally, because it doesn't destroy VMs or even seem to cause any VMs to be rebooted, but it sure does make me panic when I see that 20 VMs are going to be updated in-place when I only made only little change to a single VM. Then I realize that it's not really changing anything, but I still have to go through the list of supposed changes to make sure, so while it doesn't cause downtime, it's still pretty annoying.

I'm guessing it's not reading the bootdisk property from Proxmox or something, so I expect this will be trivial to fix once the responsible code is located.

Note: This is similar to #655 (which was auto-closed without being fixed), however what I am seeing is much simpler. That bug ticket had many fields affected and some of them were being nulled out, whereas mine is only one field and it's showing up as being added.