https://github.com/mschuchard/linter-ansible-syntax

ansible syntax check linter for pulsar
https://github.com/mschuchard/linter-ansible-syntax

ansible atom-editor atom-package hacktoberfest linter pulsar-edit pulsar-package

Last synced: 9 days ago
JSON representation

ansible syntax check linter for pulsar

• Host: GitHub
• URL: https://github.com/mschuchard/linter-ansible-syntax
• Owner: mschuchard
• License: mit
• Created: 2016-03-24T17:11:58.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2024-09-05T13:19:45.000Z (2 months ago)
• Last Synced: 2024-11-01T19:42:23.559Z (16 days ago)
• Topics: ansible, atom-editor, atom-package, hacktoberfest, linter, pulsar-edit, pulsar-package
• Language: JavaScript
• Homepage:
• Size: 125 KB
• Stars: 5
• Watchers: 4
• Forks: 3
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
![Preview](https://raw.githubusercontent.com/mschuchard/linter-ansible-syntax/master/linter_ansible_syntax.png)

### Linter-Ansible-Syntax

Linter-Ansible-Syntax aims to provide functional and robust Ansible syntax check linting functionality within Pulsar.

This package is now in maintenance mode. All feature requests and bug reports in the Github repository issue tracker will receive a response, and possibly also be implemented (especially bug fixes). However, active development on this package has ceased.

### Installation

Ansible version >= 2.0 is required to be installed before using this. The Atom-IDE-UI and Language-Ansible packages are also required.

All testing is performed with the latest stable version of Pulsar. Any version of Atom or any pre-release version of Pulsar is not supported.

### Usage

- The Ansible syntax check only outputs the first error it encounters, and therefore only the first error in a playbook will be displayed.

- Pulsar uses a legacy version of Node, and a bug within that version no longer permits this linter to capture Ansible warnings.

- The Ansible syntax check functionality is only operable on a playbook. If your playbook contains roles and/or includes anywhere in the playbook, then these will be checked as well.

- To quickly and easily access issues in other files, you will need to change the settings inside Linter-UI-Default. For `Panel Represents` and/or `Statusbar Represents`, you will need to change their options to `Entire Project`. This will allow you to use either display to quickly access issues in other files by clicking on the displayed information.