Files
computer-playbook/tests/integration/ansible/playbooks/README.md
kevinveenbirkenbachandClaude Opus 5 351b64e2c5 refactor(deploy): resolve role groups at runtime instead of generating task files
`cli build include` generated one tasks/groups/<group>-roles.yml per invokable category during setup, and the stage plays included those files. They were written by the in-container UID, which is why a dedicated clean-container-owned helper had to delete them from inside the container.

The stage plays now loop over lookup('group_roles', <group>) and include tasks/utils/setup/{group,role}.yml directly. ordered_roles() in utils/roles/order.py holds the run_after topological sort the generator used to perform at build time.

utils/roles/stage.py:_group_names() no longer globs the generated files; it reads get_invokable_paths(), the same categories.yml source those files were derived from.

Measured: handlers still flush after every role (ansible-core 2.20.2, three loop items, three separate handler runs), and resolving all 18 groups costs 0.60s cold against 1.4s for the generator.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-12 23:21:34 +02:00

626 B

Playbook Tests 🎬

Integration tests for playbook-level wiring: tasks/stages/**, invokable-path coverage, and the dispatch between them.

Tests in this directory MUST only cover rules about how playbooks invoke role groups and how the invokable-paths filter maps to stages. Tests for role-internal meta/main.yml MUST live under roles/meta/; tests for include/import target existence MUST live under roles/includes/.

For framework, directory layout, and make test-integration usage see integration.md.