Using Github Action to Lint Ansible

Discover how to automate Ansible playbook linting using GitHub Actions, helping you maintain code standards by running ansible-lint on every push. Learn to create and configure workflows that integrate lint checks seamlessly into your CI CD pipeline.

We'll cover the following...

Create a lint workflow
Try it now

Fix all Ansible lint flags
Update Docker image

Remembering to run ansible-lint before you push code won’t happen. That’s why you have the computer do it for you, which means using a Github action to lint your playbooks every time you push code.

Github actions automate, customize, and execute software development work from right in our repository. You can create actions yourself, or you can leverage open-source actions created by others.

Github workflows are how you link actions together into a series of tasks. Both actions and workflows are defined by YAML files and stored in the .github directory within your repository.

Create a lint workflow

Ansible (the company) has an open-source action called Ansible Lint for GitHub Action that you will use within a workflow to lint all your Ansible ...

1.Getting Started

2.Ansible Development with Containers

3.Connect to the Cloud

4.Starting at the Source

5.Getting Started with Ad-Hoc Commands and Playbooks

6.Deploy an Ansible Development Environment

7.Putting the Ansible Environment to Work

8.Take Inventory of the Infrastructure

9.Build Reusable Configurations

10.Dynamic Inventories for Scaling

11.Build a CI \ CD pipeline for Ansible with Github Actions

12.Appendix

Using Github Action to Lint Ansible

Create a lint workflow