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 <copilot@github.com>
This commit is contained in:
@@ -17,5 +17,6 @@ jobs:
|
|||||||
uses: ansible/ansible-lint@665d9e07a1943254d2910faffc106adaf7ea7294 # v26.8.0
|
uses: ansible/ansible-lint@665d9e07a1943254d2910faffc106adaf7ea7294 # v26.8.0
|
||||||
with:
|
with:
|
||||||
args: "--config-file .ansible-lint"
|
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"
|
setup_python: "true"
|
||||||
|
|||||||
@@ -2,5 +2,4 @@
|
|||||||
|
|
||||||
collections:
|
collections:
|
||||||
- name: community.crypto
|
- name: community.crypto
|
||||||
- name: community.docker
|
|
||||||
- name: community.general
|
- name: community.general
|
||||||
|
|||||||
Reference in New Issue
Block a user