From e793794fdd38ddfffdc3ecc0d012423fd7d13676 Mon Sep 17 00:00:00 2001 From: Hermes Agent service account Date: Sun, 7 Jun 2026 16:58:25 -0500 Subject: [PATCH] fix(ansible): set collections_path to /opt/ansible-collections in ansible.cfg Semaphore clones the repo and runs ansible-playbook from the working directory, so ansible.cfg is loaded automatically. This is more reliable than env vars inherited through podman exec subprocesses. /opt/ansible-collections is bind-mounted into the container and populated by the semaphore role's collections task. --- ansible/ansible.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ansible/ansible.cfg b/ansible/ansible.cfg index 0f32415..67e3fae 100644 --- a/ansible/ansible.cfg +++ b/ansible/ansible.cfg @@ -54,7 +54,7 @@ # (pathspec) Colon-separated paths in which Ansible will search for collections content. Collections must be in nested *subdirectories*, not directly in these directories. For example, if ``COLLECTIONS_PATHS`` includes ``'{{ ANSIBLE_HOME ~ "/collections" }}'``, and you want to add ``my.collection`` to that directory, it must be saved as ``'{{ ANSIBLE_HOME} ~ "/collections/ansible_collections/my/collection" }}'``. -;collections_path=/Users/rblundon/.ansible/collections:/usr/share/ansible/collections +collections_path=/opt/ansible-collections:/usr/share/ansible/collections # (boolean) A boolean to enable or disable scanning the sys.path for installed collections. ;collections_scan_sys_path=True