[GH-ISSUE #330] Unable to Delete guest with `protection` set to `true` #77

New issue

Open

opened 2026-02-28 00:40:28 +03:00 by kerem · 1 comment

kerem commented

2026-02-28 00:40:28 +03:00

Owner

Originally created by @Tinyblargon on GitHub (Apr 24, 2024).
Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/330

Originally assigned to: @Tinyblargon on GitHub.

Originally created by @Tinyblargon on GitHub (Apr 24, 2024). Original GitHub issue: https://github.com/Telmate/proxmox-api-go/issues/330 Originally assigned to: @Tinyblargon on GitHub.

kerem added the

type/bug

label

2026-02-28 00:40:28 +03:00

kerem commented

2026-02-28 00:40:29 +03:00

Author

Owner

@maksimsamt commented on GitHub (Jun 13, 2024):

@Tinyblargon,

This is the intended behavior of Proxmox VM operation, as per official documentation:

protection: (default = 0)
Sets the protection flag of the VM. This will disable the remove VM and remove disk operations.

How and why do you plan to delete a VM with protection enabled (true)?

I think it should stay that way, when it’s impossible to remove VM with terraform destroy and protection = true

@maksimsamt commented on GitHub (Jun 13, 2024): @Tinyblargon, This is the intended behavior of Proxmox VM operation, as per [official documentation](https://pve.proxmox.com/pve-docs/pve-admin-guide.html#qm_configuration): >protection: <boolean> (default = 0) >Sets the protection flag of the VM. This will disable the remove VM and remove disk operations. How and why do you plan to delete a VM with `protection` enabled (true)? I think it should stay that way, when it’s impossible to remove VM with `terraform destroy` and `protection = true`

kerem referenced this issue

2026-02-28 00:41:07 +03:00

[PR #77] [MERGED] setting features is allowed only for root, so don't do it unless explicitly asked #209