ansible/plays/archived/ contains still-runnable destructive plays with no confirmation guard:
remove_ceph_cpool.yml:43-44 - zfs destroy -rf looped over matching volumes on hosts: pve_cluster (whole Proxmox cluster).
cleanup-gitea-mess.yml:19-39 - deletes the gitea service/binary/config/user on hosts: all:!gitea.srv.renner.uno.
Both execute immediately if invoked despite living in an "archived" directory.
Fix
Added the same fail-task safety-switch pattern already used in ansible/plays/update-dist-upgrade.yml (confirm_upgrade) to both plays: a confirm_destroy var defaulting to false, with a Safety Check task that fails immediately unless the play is run with -e 'confirm_destroy=true'.
Verification
ansible-playbook --syntax-check passes on both modified files.
Fixes #207
## Problem
ansible/plays/archived/ contains still-runnable destructive plays with no confirmation guard:
- remove_ceph_cpool.yml:43-44 - zfs destroy -rf looped over matching volumes on hosts: pve_cluster (whole Proxmox cluster).
- cleanup-gitea-mess.yml:19-39 - deletes the gitea service/binary/config/user on hosts: all:!gitea.srv.renner.uno.
Both execute immediately if invoked despite living in an "archived" directory.
## Fix
Added the same fail-task safety-switch pattern already used in ansible/plays/update-dist-upgrade.yml (confirm_upgrade) to both plays: a confirm_destroy var defaulting to false, with a Safety Check task that fails immediately unless the play is run with -e 'confirm_destroy=true'.
## Verification
ansible-playbook --syntax-check passes on both modified files.
remove_ceph_cpool.yml (fleet-wide zfs destroy on pve_cluster) and
cleanup-gitea-mess.yml (deletes gitea service/binary/config/user on
all:!gitea.srv.renner.uno) are archived but still directly runnable
with no confirmation guard. Add the same fail-task safety-switch
pattern already used in plays/update-dist-upgrade.yml, requiring
-e 'confirm_destroy=true' before either play executes.
Fixes#207
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Fixes #207
Problem
ansible/plays/archived/ contains still-runnable destructive plays with no confirmation guard:
Both execute immediately if invoked despite living in an "archived" directory.
Fix
Added the same fail-task safety-switch pattern already used in ansible/plays/update-dist-upgrade.yml (confirm_upgrade) to both plays: a confirm_destroy var defaulting to false, with a Safety Check task that fails immediately unless the play is run with -e 'confirm_destroy=true'.
Verification
ansible-playbook --syntax-check passes on both modified files.