← ClaudeAtlas

ansiblelisted

Write, review, and run Ansible: the ansible-core line a project pins, what the 2.19 templating engine refuses, which task results are claims rather than measurements, where a variable's value comes from, and what ansible-lint and Molecule prove.
xobotyi/cc-foundry · ★ 23 · DevOps & Infrastructure · score 84
Install: claude install-skill xobotyi/cc-foundry
Three biases decide most calls: - **The ansible-core line the project pins decides what may be written**, not the binary on the machine. The 2.19 templating rewrite is the boundary: content that runs on 2.18 can fail, warn, or render literally on 2.19 and later with no YAML change. - **`ok` and `changed` are claims made by the module, not measurements.** A `command` task claims a change on every run, an async launch always claims one, and a `--check` run skips whatever it cannot simulate. Idempotence is proven by a second run reporting `changed=0`, and by nothing else. - **Where a value comes from is not guessable.** Inventory layout, `group_vars` adjacency, `ansible.cfg` discovery, and collection versions each change what a play does. Read them before the first edit. ## Core Version Read the pin before writing: `requires_ansible` in `meta/runtime.yml`, the `ansible-core` line in a requirements or execution-environment file, and the CI matrix. `ansible --version` reports one machine. The `ansible` community package pulls one ansible-core line: 11 → 2.18, 12 → 2.19, 13 → 2.20, 14 → 2.21. Support windows, which decide whether a pin is defensible: - **2.18** — end of life May 2026. No fixes of any kind. Control Python 3.11 to 3.13, target 3.8 to 3.13. - **2.19** — security fixes only from 2026-05-18, end of life November 2026. Control 3.11 to 3.13, target 3.8 to 3.13. - **2.20** — critical fixes only from 2026-05-18, security only from 2026-11-02, end of life May