Skip to content

Choose activation when creating a container cleanup policy #509

Description

@sjungwon03

Extend the disabled-first cleanup policy creation flow with an explicit optional activation choice. Keep disabled as the default; confirm project-wide scheduled tag deletion risk and exact criteria before submitting enabled=true. Reset acknowledgement after any edit, preserve stale-policy preflight and pending guards, and cover enabled/disabled payloads and responsive localized confirmation with test-first regression tests. Existing policy creation prerequisite: #469 / #470. Atomic create-only semantics and live-instance validation remain separate.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions