mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 4.7
16e290c9ed
The first reuse-kept deploy after introducing `database_query` failed with `couldn't resolve module/action 'database_query'`: ansible only searches for custom modules along the `library` config path, and the module had landed under `plugins/modules/` (collection-style layout) without that path being registered in ansible.cfg. Realign with the repo's existing convention — `library/cert_check_exists.py` and `library/docker_bridge_gateway.py` are already there — by relocating the module to `library/database_query.py`. Make the search path explicit in ansible.cfg (`library = ./library`) instead of relying on ansible's implicit playbook-adjacent discovery, so the resolver stays predictable across CLI / playbook / role-include entry points. Move the unit suite into `tests/unit/library/` alongside the moved module, fix the doc-string reference in the lint guard that points callers at the canonical module location, and drop the now-empty `tests/unit/plugins/modules/` package. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 lines
83 B
Python
4 lines
83 B
Python
from pathlib import Path
|
|
|
|
PROJECT_ROOT: Path = Path(__file__).resolve().parents[3]
|