From 03f77e69d6e13fccda147a0e89db53b8a0befcce Mon Sep 17 00:00:00 2001 From: Markus Pesch Date: Tue, 8 Sep 2026 11:24:57 +0200 Subject: [PATCH] refactor(ci): keep community.docker out of the role requirements The collection community.docker is only used by the molecule scenario and is no runtime dependency of the role. It is therefore declared in molecule/default/collections.yml only. Since ansible-lint also lints the scenario, the action installs that file instead of requirements.yaml. Co-authored-by: Copilot --- .gitea/workflows/ansible-linters.yaml | 3 ++- requirements.yaml | 1 - 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/ansible-linters.yaml b/.gitea/workflows/ansible-linters.yaml index a9aea56..c8316ff 100644 --- a/.gitea/workflows/ansible-linters.yaml +++ b/.gitea/workflows/ansible-linters.yaml @@ -17,5 +17,6 @@ jobs: uses: ansible/ansible-lint@665d9e07a1943254d2910faffc106adaf7ea7294 # v26.8.0 with: args: "--config-file .ansible-lint" - requirements_file: "requirements.yaml" + # The molecule scenario is linted as well, so its collections are required beside the ones of the role. + requirements_file: "molecule/default/collections.yml" setup_python: "true" diff --git a/requirements.yaml b/requirements.yaml index 7943412..b6179f0 100644 --- a/requirements.yaml +++ b/requirements.yaml @@ -2,5 +2,4 @@ collections: - name: community.crypto -- name: community.docker - name: community.general