ansible-lint does not only lint the role but the molecule scenario as well, and the scenario creates its containers with community.docker. Only the runtime requirements of the role were installed, so the linter could not resolve community.docker.docker_container and failed the syntax check. The collection list of the scenario is a superset of the runtime requirements, therefore it is used instead of adding a test only dependency to requirements.yml. Co-authored-by: Copilot <copilot@github.com>
23 lines
668 B
YAML
23 lines
668 B
YAML
name: Ansible Linter
|
|
|
|
on:
|
|
pull_request:
|
|
types: [ "opened", "reopened", "synchronize" ]
|
|
push:
|
|
branches: [ '**' ]
|
|
tags-ignore: [ '**' ]
|
|
|
|
jobs:
|
|
ansible-lint:
|
|
runs-on:
|
|
- ubuntu-latest
|
|
steps:
|
|
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0
|
|
- name: Run ansible-lint
|
|
uses: ansible/ansible-lint@665d9e07a1943254d2910faffc106adaf7ea7294 # v26.8.0
|
|
with:
|
|
args: "--config-file .ansible-lint"
|
|
# 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"
|