Will Thames
Will Thames
Does this need anything more than the first couple of paragraphs from http://willthames.github.io/2016/06/28/announcing-ansible-review.html If not I'll just add that as an introduction to the README
"Why have ansible-lint in the first place" ignores history somewhat. It was around for a good few years before ansible-review. But perhaps you meant "Why continue to provide ansible-lint" ansible-lint...
@wilmardo I think that for your use case, ansible-review should work well as an alternative to ansible-lint - it's just a matter of coming up with the standards.py that you...
In the general response to this ticket, yes, I should definitely write some stronger documentation about support policies and purposes. In the main, ansible-lint should be considered bug fix only...
The main difference is that ansible-review is designed for code reviews and is designed to be a little more configurable (there are fewer constraints on the kinds of resources that...
Yeah, that's a difficult one. I'm really a little unsure as to better do this. Currently the pragmatic way is to add module directories to the `ANSIBLE_LIBRARY` path. I know...
I'd definitely favourably consider a PR that implemented that idea @ssbarnea
If there is a PR that would fix this, let me know. I've had a rereview of #28 but that needs a rebase and I'm still not convinced by the...
There's already a lint for octal permissions in ansible-lint for this precise reason. Use that one!
Can you provide an example failing playbook please?