Specifying Rules at Runtime

By default, ansible-lint uses the rules found in ansible-lint/src/ansiblelint/rules. To override this behavior and use a custom set of rules, use the -r /path/to/custom-rules option to provide a directory path containing the custom rules. For multiple rule sets, pass multiple -r options.

It’s also possible to use the default rules, plus custom rules. This can be done by passing the -R to indicate that the default rules are to be used, along with one or more -r options.

Using Tags to Include Rules

Each rule has an associated set of one or more tags. To view the list of tags for each available rule, use the -T option.

The following shows the available tags in an example set of rules, and the rules associated with each tag:

$ ansible-lint -v -T
# List of tags and rules they cover
command-shell:  # Specific to use of command and shell modules
  - command-instead-of-module
  - command-instead-of-shell
  - deprecated-command-syntax
  - inline-env-var
  - no-changed-when
  - risky-shell-pipe
core:  # Related to internal implementation of the linter
  - internal-error
  - load-failure
  - parser-error
  - syntax-check
deprecations:  # Indicate use of features that are removed from Ansible
  - deprecated-bare-vars
  - deprecated-command-syntax
  - deprecated-local-action
  - deprecated-module
  - no-jinja-when
  - role-name
experimental:  # Newly introduced rules, by default triggering only warnings
  - fqcn-builtins
  - ignore-errors
  - no-log-password
  - risky-file-permissions
  - var-naming
formatting:  # Related to code-style
  - fqcn-builtins
  - no-jinja-nesting
  - no-tabs
  - playbook-extension
  - risky-octal
  - var-spacing
  - yaml
idempotency:  # Possible indication that consequent runs would produce different results
  - git-latest
  - hg-latest
  - no-changed-when
  - package-latest
idiom:  # Anti-pattern detected, likely to cause undesired behavior
  - command-instead-of-module
  - command-instead-of-shell
  - empty-string-compare
  - inline-env-var
  - literal-compare
  - no-handler
  - no-loop-var-prefix
  - no-relative-paths
  - unnamed-task
  - var-naming
metadata:  # Invalid metadata, likely related to galaxy, collections or roles
  - meta-incorrect
  - meta-no-info
  - meta-no-tags
  - meta-video-links
  - role-name
  - fqcn-builtins
  - no-log-password
  - no-same-owner
  - no-log-password
  - ignore-errors
  - partial-become
  - risky-file-permissions
  - syntax-check
yaml:  # External linter which will also produce its own rule codes.
  - yaml

To run just the idempotency rules, for example, run the following:

$ ansible-lint -t idempotency playbook.yml

Excluding Rules

To exclude rules using their identifiers or tags, use the -x SKIP_LIST option. For example, the following runs all of the rules except those with the tags formatting and metadata:

$ ansible-lint -x formatting,metadata playbook.yml

Ignoring Rules

To only warn about rules, use the -w WARN_LIST option. In this example all rules are run, but if rules with the experimental tag match they only show an error message but don’t change the exit code:

$ ansible-lint -w experimental playbook.yml

The default value for WARN_LIST is ['experimental'] if you don’t define your own either on the cli or in the config file. If you do define your own WARN_LIST you will need to add 'experimental' to it if you don’t want experimental rules to change your exit code.

False Positives: Skipping Rules

Some rules are a bit of a rule of thumb. Advanced git, yum or apt usage, for example, is typically difficult to achieve through the modules. In this case, you should mark the task so that warnings aren’t produced.

To skip a specific rule for a specific task, inside your ansible yaml add # noqa [rule_id] at the end of the line. If the rule is task-based (most are), add at the end of any line in the task. You can skip multiple rules via a space-separated list.

- name: this would typically fire git-latest and partial-become
  become_user: alice  # noqa git-latest partial-become
  git: src=/path/to/git/repo dest=checkout

If the rule is line-based, # noqa [rule_id] must be at the end of the particular line to be skipped

- name: this would typically fire LineTooLongRule 204 and var-spacing
    url:  # noqa 204
    dest: "{{dest_proj_path}}/foo.conf"  # noqa var-spacing

It’s also a good practice to comment the reasons why a task is being skipped.

If you want skip running a rule entirely, you can use either use -x command line argument, or add it to skip_list inside the configuration file.

A less-preferred method of skipping is to skip all task-based rules for a task (this does not skip line-based rules). There are two mechanisms for this: the skip_ansible_lint tag works with all tasks, and the warn parameter works with the command or shell modules only. Examples:

- name: this would typically fire deprecated-command-syntax
  command: warn=no chmod 644 X

- name: this would typically fire command-instead-of-module
  command: git pull --rebase
    warn: false

- name: this would typically fire git-latest
  git: src=/path/to/git/repo dest=checkout
  - skip_ansible_lint