fix ansible-pull successful run timestamp export and some more cleanup #185

Merged
june merged 4 commits from ansible_pull_fix_timestamp_export into main 2026-11-04 17:35:22 +01:00

2026-11-04

ansible-pull(role): deploy failure notify service using the copy loop
All checks were successful
/ build (pull_request) Successful in 32s
/ build (push) Successful in 37s
/ cleanup-staging (pull_request) Successful in 41s
/ Ansible Lint (pull_request) Successful in 3m47s
/ Ansible Lint (push) Successful in 3m45s
Deploy the ansible-pull-failure-notify.service using the loop using
ansible.builtin.copy as it doesn't have any template logic.
2026-11-04 17:28:05 +01:00
ansible-pull(role): have failure notify deploy match other script deploy
Have the deployment of the ansible-pull-failure-notify script match the
deployment of the other helper scripts.
2026-11-04 17:28:05 +01:00
ansible-pull(role): move ansible-pull reboot logic to script as well
Do this to unify the way these helper scripts get deployed.
2026-11-04 17:28:05 +01:00
ansible-pull(role): make successful run timestamp exporter work
The successful run timestamp exporter didn't work, because the
ansible-pull user wouldn't necessarily have the necessary permissions
and because the command wouldn't properly work.
Move the timestamp export as well as the reboot to separate services,
which always run as root, to ensure these operations work and to have a
clean setup using systemd services.
Also move the successful run timestamp exporter to a custom script to
have it work properly.
2026-11-04 17:28:03 +01:00