Pavel Boldyrev

Ah, I see. You're right about: > ... you cannot set whether the device is added as eth0 or eth1. This is a key limitation of the current provider's design....

Remove this functionality as per https://github.com/bpg/terraform-provider-proxmox/issues/1291#issuecomment-2111376422

That will be a good change for v1.0: #1231

That should work to prevent VM movement or recreation by the provider if no VM attributes have changed. However, if there is an update to a VM, and the VM...

Thanks @elias314 for testing and further analysis. It actually makes sense that the `lifecycle` workaround works for most cases, even for the VM update. The PVE UI allows you to...

> > That could be one solution, but from the note above, its probably not even necessary. I think a way out of this mess would be simply treating `node_name`...

While I understand the intention to use the provider as a frontend and load balancer for the Proxmox cluster, which is essentially what this ticket suggests, this is not functionality...

Hi @marton-gombocz! 👋🏼 Before deciding on this ticket, I'd like to know a bit more about your error cases: >The problem is that if I enable guest agent checking and...

Hi @maxexcloo! 👋🏼 I'm not quite sure what problem you're trying to solve with this enhancement. Is it about deploying different resources to different nodes in a cluster? If that's...

Hi @maxexcloo, have you tried [provider aliases](https://developer.hashicorp.com/terraform/language/providers/configuration#alias-multiple-provider-configurations)?