Open maksimsamt opened 3 months ago
@maksimsamt The protection is about the protection flag in proxmox. That you can't delete it with it enabled is a known issue https://github.com/Telmate/proxmox-api-go/issues/330
@Tinyblargon,
The protection is about the protection flag in proxmox
Thanks, got it.
That you can't delete it with it enabled is a known issue
Isn't this expected behavior? This is exactly the behavior I expect...
But what about this?
Everything looks fine, but this action causes VM to shutdown. I expected that in protection mode VM state would remain untouched, for example, keeps running.
This issue is stale because it has been open for 60 days with no activity. Please update the provider to the latest version and, in the issue persist, provide full configuration and debug logs
still actual:
Everything looks fine, but this action causes VM to shutdown. I expected that in protection mode VM state would remain untouched, for example, keeps running.
System details:
As per documentation:
Setting this value to
true
and runningterraform destroy
gives the following result:Everything looks fine, but this action causes VM to shutdown.
I expected that in protection mode VM state would remain untouched, for example, keeps running.
The second thing, is
protection
argument redundant? (resolved, not redundant, answer https://github.com/Telmate/terraform-provider-proxmox/issues/1043#issuecomment-2162658126)Cause that protection from destroy can be achieved using Terraform built-in lifecycle meta-argument, for example:
In this case gives such result: