timeouts does not apply all the time about terraform-provider-proxmox HOT 2 OPEN

Yes, sorry if I wasn't clear enough.
I'm updating an existing VM in this example (CPU core count from 2 to 3 but can be any resource value)
Yes, the VM is running the second time.
Its a VM cloned from a template.
Agent is disabled to trigger timeout.
The original issue was that our network has problems sometimes and we have failed Pulumi runs because of that. Its really hard to do a re-try if you have to wait 1800 Sec in case of an issue.
So I lowered the timeouts when I noticed the problem. To simulate a network issue, I just disable the Agent because I noticed that the behavior is the same in both cases.

from terraform-provider-proxmox.

Hi @miberecz 👋🏼

Sorry, I don't fully understand your use case. Are you trying to delete the existing VM? Or applying a change that causes a VM to be re-created (hence there is see "destroying..." in the output)?
Is the VM running when you call apply second time?
Is the VM cloned from a template, or a standalone one?
You don't have agent enabled, was it on purpose to trigger the timeout?

There are many different timeout in the code, and it is important to understand the use case to identify which one (or combination of them) do not work as expected.
Could you please provide a bit more details?

from terraform-provider-proxmox.