Re-imported cloned VM does not match the original plan about terraform-provider-proxmox HOT 2 CLOSED

Hey!
Yep, i suspected it won't be an easy solution :D
My case involves 2 possible scenarios:

• We have several directory separated environments with dedicated state file each. So person who's helping me manage Proxmox created a VMs in the wrong environment and i wanted to move them into a correct one by removing resources in the initial state and importing in the correct one.
• Second possible scenario is to try to move already existing manually created VMs under terraform management. It so happened that before i wrote a module some people used to create VMs in GUI so they're "unmanaged" now. I don't remember if i tried that yet though but i thought that i could try to use that on VMs created manually from my module's templates.

Overall i don't really need to know clone's source - i just want my imported VMs to stay and not be re-provisioned by terraform plan. Actually, maybe i could use 'lifecycle' argument for that. Something like this:

  lifecycle {
    ignore_changes = [
      clone
    ]
  }

UPD.
Yep, it works. At least there's no detected changes in resource that would force re-provision. It would make impossible to re-provision resource by changing clone source of course but i already had 'clone[0].vm_id' in there actually - i guess in case my template VMs change their vm_id (they receive it dynamically and i sometimes re-create these templates with updated images). So it's no biggie.
I suppose we could close this one if you don't have anything to add, i really enjoy your explanations. It is nice to talk to smart people :)

from terraform-provider-proxmox.

This problem is similar to what I was trying to explain in #1134 (comment)
Basically, any information about the clone source (particularly in the case of a full clone) is completely transient and is not stored in the VM. So there is no way to read it back during the import.

But I'm more curious about the actual use case, why you may need to know the clone's source? Are you planning on updating the source and then have those updates automatically reflected in the clone?
Or is it a case of disaster recovery, when you have a previously applied plan, but the state is lost and you're recovering the state?

If the usage scenario is an edge case, then I'd say, manually editing the imported state and/or plan to reconcile them is a viable option.

from terraform-provider-proxmox.