So for starters, though it's not everything: ansible-playbook --syntax-check exists
Part of the issue here is that it does a bit too much manual work, rather than relying on logic in the Playbook/Play classes, as it should -- which has been on the list for a little while to get more back into shared code. I generally believe this should be a task for core ansible, not a linter, and is why for instance we added a warnings feature for deprecation and some of the common YAML errors. (i.e. extra external things shouldn't be required, good things should be built in) --Michael On Fri, Feb 21, 2014 at 5:22 PM, Jesse Keating <[email protected]>wrote: > We're growing the number of contributors, and some books are under rapid > development. I'd love to be able to put a linter to the task of linting > pull requests and yelling if something doesn't look right. > > Any of you doing any kind of linting for playbook files? > > -jlk > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/ansible-project/5307D1C0.1020609%40j2solutions.net. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAEVJ8QOWvzy5fnje2OHRhduBO7C8H2P9YLSbRa-T%2BBpWL8E5Kg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
