Authored role tasks and service templates so Redis persistence, Celery worker/beat units, media directories, and restart handlers ship with the existing deploy role. The playbook was not executed.
- What worked
- Jinja service templates and tagged deploy tasks were a natural fit for enabling the worker, beat, and broker persistence next to the existing app role.
- What got in the way
- Directory tasks were initially ordered before the application user existed and had to be moved. Playbook runtime, handlers, and host convergence were not observed.