Skip to content

purge_on_destroy parity for CTs #2842

@MikeBishop

Description

@MikeBishop

Is your feature request related to a problem? Please describe.
Some of my LXCs and the HA policies for them live in different modules. When the module that owns the LXC tries to destroy it, it fails because the HA policy exists and the purge option wasn't passed; the module that owns the HA policy doesn't destroy it because the LXC still exists.

Describe the solution you'd like
#2118 added purge_on_destroy as an option for VMs; the error message suggests that setting the purge option would bypass this conflict. However, proxmox_virtual_environment_container doesn't have equivalent options.

Describe alternatives you've considered
I'd need to add more shared state across modules to control the destroy ordering.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions