name: Ansible Lint
on:
  - pull_request
  - push

jobs:
  build-ansible:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Lint Ansible playbooks
        # Lastest commit, as of February 22, 2021
        uses: ansible/ansible-lint-action@c37fb7b4bda2c8cb18f4942716bae9f11b0dc9bc
        with:
          override-deps: |
            ansible==2.9
            ansible-lint==4.3.0
          targets: |
            scripts/ansible/kill_playbook.yml
            scripts/ansible/ping_playbook.yml
            scripts/ansible/restart_playbook.yml
            scripts/ansible/service_playbook.yml
            scripts/ansible/update_playbook.yml

          args:
            -c scripts/ansible/.ansible-lint

name: Ansible Lint
on:
  - pull_request
  - push

jobs:
  build-ansible:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v2

      - name: Lint Ansible playbooks
        # Lastest commit, as of February 22, 2021
        uses: ansible/ansible-lint-action@c37fb7b4bda2c8cb18f4942716bae9f11b0dc9bc
        with:
          targets: |
            scripts/ansible/kill_playbook.yml
            scripts/ansible/ping_playbook.yml
            scripts/ansible/restart_playbook.yml
            scripts/ansible/service_playbook.yml
            scripts/ansible/update_playbook.yml

          args:
            -c scripts/ansible/.ansible-lint

Remove version pins in Ansible Lint CI
ansible: Remove version pins in Ansible Lint CI

These were added by me when I erroneously thought old versions of
Ansible Lint misdetected rule 208 on tasks with

	{file: {path: foo, state: directory}}

in fact this rule was a new addition in Ansible Lint 4.3.0. Removing
these pins means that the CI workflow will use the latest released
versions, which is usually desirable.
