ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Sublime​Linter-contrib-ansible-lint

by mliljedahl ST3

SublimeLinter plugin for Ansible, using ansible-lint.

Details

Installs

  • Total 1K
  • Win 315
  • OS X 438
  • Linux 315
Oct 20 Oct 19 Oct 18 Oct 17 Oct 16 Oct 15 Oct 14 Oct 13 Oct 12 Oct 11 Oct 10 Oct 9 Oct 8 Oct 7 Oct 6 Oct 5 Oct 4 Oct 3 Oct 2 Oct 1 Sep 30 Sep 29 Sep 28 Sep 27 Sep 26 Sep 25 Sep 24 Sep 23 Sep 22 Sep 21 Sep 20 Sep 19 Sep 18 Sep 17 Sep 16 Sep 15 Sep 14 Sep 13 Sep 12 Sep 11 Sep 10 Sep 9 Sep 8 Sep 7 Sep 6 Sep 5
Windows 0 4 4 3 4 0 0 1 3 3 0 3 1 3 4 2 1 1 0 0 0 2 3 2 1 2 1 1 2 2 3 1 3 0 4 8 2 2 4 0 1 1 3 0 4 0
OS X 2 3 3 2 3 2 0 3 4 3 1 4 0 4 0 4 3 5 6 1 3 1 5 5 0 3 2 0 7 5 2 6 3 1 4 4 7 4 2 1 1 1 2 1 3 2
Linux 1 3 1 3 1 4 0 1 1 0 2 2 3 1 3 4 7 1 1 2 1 1 0 2 3 1 0 1 3 0 4 3 7 3 0 4 3 4 4 1 3 0 4 0 3 1

Readme

Source
raw.​githubusercontent.​com

SublimeLinter-contrib-ansible-lint

Build Status

This linter plugin for SublimeLinter provides an interface to ansible-lint. It will be used with files that have the “Ansible” syntax.

Installation

SublimeLinter 3 must be installed in order to use this plugin. If SublimeLinter 3 is not installed, please follow the instructions here.

Linter installation

Before using this plugin, you must ensure that ansible-lint is installed on your system. To install ansible-lint, do the following:

  1. Install Python and pip.

  2. Install ansible-lint by typing the following in a terminal:

[sudo] pip install ansible-lint

Note: This plugin requires ansible-lint 3.0.1 or later.

Syntax installation

Also ensure that Ansible is installed in Sublime Text. To install Ansible, do the following:

To install via Package Control, do the following:

  1. Within Sublime Text, bring up the Command Palette and type install. Among the commands you should see Package Control: Install Package. If that command is not highlighted, use the keyboard or mouse to select it. There will be a pause of a few seconds while Package Control fetches the list of available plugins.

  2. When the plugin list appears, type ansible. Among the entries you should see Ansible. If that entry is not highlighted, use the keyboard or mouse to select it.

Note: If Ansible syntax is not installed this plugin will not work.

Syntax configuration

To be able to automatically open the .yml files in an Ansible project with the Ansible syntax, ApplySyntax needs to be configured with the settings below. If this is not done the .yml files will be opend with the YAML syntax and the linter plugin will not work without manually change the syntax for every file.

The settings can be found under:

Sublime Text -> Preferences -> Package Settings -> ApplySyntax -> Settings - User
"syntaxes": [{
        "name": "Ansible/Ansible",
        "rules": [
          {"file_name": ".*/tasks/.*.yml$"},
          {"file_name": ".*/handler/.*.yml$"},
          {"file_name": ".*/*_vars/.*.yml$"},
          {"file_name": ".*/roles/.*.yml$"},
          {"file_name": ".*/playbooks/.*.yml$"},
          {"file_name": ".*/.*ansible.*/.*.yml$"}
        ]
      }]

Linter configuration

In order for ansible-lint to be executed by SublimeLinter, you must ensure that its path is available to SublimeLinter. Before going any further, please read and follow the steps in “Finding a linter executable” through “Validating your PATH” in the documentation.

Once you have installed and configured ansible-lint, you can proceed to install the SublimeLinter-contrib-ansible-lint plugin if it is not yet installed.

Plugin installation

Please use Package Control to install the linter plugin. This will ensure that the plugin will be updated when new versions are available. If you want to install from source so you can modify the source code, you probably know what you are doing so we won’t cover that here.

To install via Package Control, do the following:

  1. Within Sublime Text, bring up the Command Palette and type install. Among the commands you should see Package Control: Install Package. If that command is not highlighted, use the keyboard or mouse to select it. There will be a pause of a few seconds while Package Control fetches the list of available plugins.

  2. When the plugin list appears, type ansible-lint. Among the entries you should see SublimeLinter-contrib-ansible-lint. If that entry is not highlighted, use the keyboard or mouse to select it.

Recommended plugin

It is highly recommended to also install the Sublime plugin Trailing Spaces by using Package Control. And to set the Trim On Save option to true.

The settings can be found under:

Sublime Text -> Preferences -> Settings
{ "trailing_spaces_trim_on_save": true }

Settings

For general information on how SublimeLinter works with settings, please see Settings. For information on generic linter settings, please see Linter Settings.

In addition to the standard SublimeLinter settings, SublimeLinter-contrib-ansible-lint provides its own settings. Those marked as “Inline Setting” or “Inline Override” may also be used inline.

Setting Description Inline Setting Inline Override
r Specify one or more rules directories using one or more -r arguments. Any -r flags override the default rules in /usr/local/lib/python2.7/dist-packages/ansiblelint/rules, unless -R is also used.
R Use default rules in /usr/local/lib/python2.7/dist-packages/ansiblelint/rules in addition to any extra rules directories specified with -r. There is no need to specify this if no -r flags are used.
t Only check rules whose id/tags match these values.
x Only check rules whose id/tags do not match these values.
exclude Path to directories or files to skip.

List of all tags

Tags IDs
behaviour ANSIBLE0016
bug ANSIBLE0014
deprecated ANSIBLE0018, ANSIBLE0015, ANSIBLE0008
formatting ANSIBLE0002, ANSIBLE0009, ANSIBLE0015
idempotency ANSIBLE0012
oddity ANSIBLE0017
readability ANSIBLE0011
repeatability ANSIBLE0005, ANSIBLE0004, ANSIBLE0010
resources ANSIBLE0006, ANSIBLE0007
safety ANSIBLE0013

Contributing

If you would like to contribute enhancements or fixes, please do the following:

  1. Fork the plugin repository.
  2. Hack on a separate topic branch created from the latest master.
  3. Commit and push the topic branch.
  4. Make a pull request.
  5. Be patient. ;-)

Please note that modifications should follow these coding guidelines:

  • Indent is 4 spaces.
  • Code should pass flake8 and pep257 linters.
  • Vertical whitespace helps readability, don’t be afraid to use it.
  • Please use descriptive variable names, no abbreviations unless they are very well known.

Thank you for helping out!