Pavel Boldyrev

Hi @gustavodrodriguez 👋🏼 This is a known limitation (hence the proper error message) due to the current VM resource format. Each `disk` block is represented as an item in an...

I'm currently testing exclusively with the latest Proxmox release, but I'm sure there might be insights and experiences out there that the community can provide. If you've got any additional...

Closing due to a lack of the feedback

Hey @GuillaumeSeren 👋🏼 Just to confirm, you have only one mount point, not two, defined in the `mount_points` list? I suspect the list could end up having a valid value,...

>> As a workaround I'd suggest to define mount points explicitly without using dynamic blocks, until the issue is fixed. >I am not sure to get it right, but what...

Well, the mount point implementation is broken :( The schema does not have the actual "mount point name" (i.e., `mp0`, `mp1`) attribute, so the provider does not know for sure...

Working with lists/sets of blocks is inherently difficult in the current implementation of the provider. This is partly due to some choices made in the legacy code at the very...

Hi @mmacedo2000! 👋🏼 The migration support was added in #501, so in _theory_ this should work, however, I have not tested it for a while. How did you try migrating...

Hi @mmaced, I can't reproduce this issue in my lab. My template: ```hcl resource "proxmox_virtual_environment_vm" "ubuntu_vm" { name = "test" node_name = "pve2" vm_id = 1000 agent { enabled =...

Hey @mmaced, could you post your TF output and ideally a debug log, so I can try to debug it?