ci / test (push) Successful in 2m39s
Ansible collection that converges MeshCore repeaters through a companion radio (TCP, USB serial or BLE): admin ACL, CLI prefs, region tree, firmware facts, companion remote-CLI ACL, and the meshcore-tth extras (BLE on/off and own BLE PIN, channel-hash filter, message age, advert fairness). Every change is read, diffed, sent and read back; --check only reads. ansible-test sanity, unit tests and a galaxy build in CI. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
Instructions for an AI agent using this collection
tth.meshcore changes MeshCore repeaters over RF. They are usually part of a community network, so a wrong run is felt by others. README.md is the reference; these are the rules.
- Always
--check --difffirst and show the user the diff. Apply only after the user approves that diff. - Never put radio settings into
prefs(freq,radio,bw,sf,cr) — the module refuses them anyway. They are changed on site, never over RF: a wrong one cuts the node off for good. - The managing companion's pubkey must be in
admins; keepexpect_freqset in the transport. - The admin password goes to ansible-vault, never into the inventory, commands you print, commits or logs.
serial: 1, one repeater at a time. A lost reply is normal on RF; rerun, do not raise timeouts blindly.- Done = the second run reports 0 changes.
Developing: see README. ansible-test sanity must pass (it checks that
DOCUMENTATION matches argument_spec), plus ruff check, ruff format --check,
yamllint and the unit tests in tests/unit.