3 Commits

Include renames

Author	SHA1	Message	Date
volker.raschekandCopilot	28d4ea523d	fix: declare the dependency on the collection community.general ... On Archlinux ansible.builtin.package resolves to the module pacman, which is shipped by community.general and not by ansible-core. Without the collection the role fails with "Could not find a matching action for the pacman package manager", which surfaced in the molecule scenario as soon as only the explicitly declared collections were installed. Co-authored-by: Copilot <copilot@github.com>	2026-09-08 11:18:29 +02:00
volker.raschekandCopilot	a6e8555e13	refactor(molecule): use docker instead of podman ... The scenario now starts its containers with community.docker instead of containers.podman, because docker is the container runtime available on the CI runner. The connection plugin, the login command and the declared collections were adjusted accordingly and the docker SDK for python is installed in the workflow, since the module requires it. Co-authored-by: Copilot <copilot@github.com>	2026-09-08 10:14:20 +02:00
volker.raschekandCopilot	206c057247	chore(ci): run the molecule scenario on every push and pull request ... The scenario was only runnable by hand so far, which defeats its purpose. Podman is already installed and configured on the runners, so the job only has to add molecule itself. The repository is named ansible-role-certificate-authority while the role is named certificate_authority. Since the scenario includes the role by its name and uses the parent of the project directory as roles path, the checkout has to happen into a directory matching the role. The collections are declared in molecule/default/collections.yml instead of being installed by an explicit step. That is the path the collections invoker of molecule looks at by default, so the dependency action of the test sequence installs them for the workflow and for local runs alike. Co-authored-by: Copilot <copilot@github.com>	2026-09-07 22:30:59 +02:00