How to use Ansible Lint to scan playbooks
Are you looking at how to use Ansible Lint?
Ansible is an IT automation tool.
Ansible Lint is a command-line tool that analyzes playbook code for potential errors.
At Bobcares, we get many queries regarding Ansible, as a part of our Server Management Services.
Today, our Support Engineers will give an idea of how the linting process helps.
What is ansible-lint?
Before getting to ansible-lint, let’s have a look at Ansible.
Ansible is an open-source IT automation tool. The purpose of this tool is to configure systems, deploy software and many more.
Usually, Ansible connects to other nodes via SSH and pushes Ansible modules into them. Ansible holds its configurations in .yml files.
An important YAML file is Ansible playbook. It defines how the Ansible should work in the hosts. So errors in the YAML files can affect the working of Ansible.
This is where we make use of a command-line tool, ansible-lint. We use this command for linting playbooks or .yml files in Ansible.
A linting process runs a program that analyses code and finds potential errors in Ansible code. That is it detects the behaviors and practices that need improvement. It can detect syntax errors, undefined variables, etc.
Installing the linting tool in Ansible
Ansible-lint is a command-line tool. It does not come with the Ansible package, rather we need to install it. We can install it in various ways.
To install it using the built-in package manager in Ubuntu we use the command,
apt install ansible-lint
Since ansible-lint is a Python package we can install it using the command,
pip install ansible-lint
Now let’s see how our Support Engineers use the linting command in Ansible.
How to use ansible-lint?
To obtain complete information on using the linting command, we use,
And the output appears as,
There many default rules used while linting a playbook. To list them, we use the command,
There are a total of 18 default rules. A few rules are,
ANSIBLE0002: Trailing whitespace There should not be any trailing whitespace ANSIBLE0004: Git checkouts must contain explicit version All version control checkouts must point to an explicit commit or tag, not just "latest" ANSIBLE0005: Mercurial checkouts must contain explicit revision All version control checkouts must point to an explicit commit or tag, not just "latest" ANSIBLE0006: Using command rather than module Executing a command when there is an Ansible module is generally a bad idea ANSIBLE0007: Using command rather than an argument to e.g. file Executing a command when there is are arguments to modules is generally a bad idea ANSIBLE0008: Deprecated sudo Instead of sudo/sudo_user, use become/become_user. . . .
For instance, if a playbook has trailing whitespace, the linting output shows up as,
Here the output lists the violated rule along with the exact line number where it occurred.
Likewise, the syntax errors in playbook appear as,
Syntax Error while loading YAML. did not find expected '-' indicator The error appears to be in '/etc/ansible/playbook.yml': line 14, column 6, but may be elsewhere in the file depending on the exact syntax problem. The offending line appears to be: name: Disable SELinux ^ here
Here it displays the offending line along with exact error.
Most importantly, a user should run the linting command in the same location as that of the .yml file.
To scan all the .yml file in the location we can use the command,
How to custom configure it?
Next, let’s see the possibility of custom configuring the linting tool.
We can custom configure ansible-lint for our requirement. Apart from the default rules, we can specify additional rules in a file.
And the command-line flag -c <file path> will lint the playbook based on the custom configuration.
[Need assistance in using Ansible lint? – We can help you.]
So far, we saw how to use the ansible-lint command-line tool. Today, our Support Engineers gave a complete guide on its installation, usage, and configuration.