mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 10:59:59 +00:00
kevinveenbirkenbach
91320b8deb
main.yml now reads as the chronological sequence it describes: it includes 01_fullstack.yml, then the single IS_STACK_HOST-gated 02_manager_ops.yml, whose substeps live in the matching 02_manager_ops/ directory numbered in execution order. The plugin pipeline moves under its parent step so its include resolves against its own directory instead of an inherited search root. The flush that deploys the stack moves out of the config step to the top of 02_manager_ops.yml. It previously ran after the swarm resolver, which then waited 600 times for a service that did not exist yet and killed two CI jobs with "no such service: nextcloud_nextcloud". The second flush and the re-resolve behind it are removed: neither included file notifies a handler, so they could never fire. A new lint pins what made this refactor risky. A relative include is resolved at runtime, so a typo or a moved file survives ansible-lint and --syntax-check and only fails mid-deploy; worse, a bare name that matches under two search roots silently shadows one file with the other. Comments that only narrated code are dropped from the addon hooks and the plugin install step.
2 lines
4 B
YAML
2 lines
4 B
YAML
---
|