ansible-lint needs option to treat warnings as errors

[ssbarnea]

We discovered that ansible-lint has no option for treating warnings as errors which is a real issue on CI environments as warnings are often ignored and lower quality code goes in.

Few examples of warnings:

• WARNING: Couldn't open <...> - No such file or directory
• [WARNING]: While constructing a mapping from ... duplicate dict key (size). Using last defined value only.

[DanyC97]

for that i guess you can use ansible-reivew ?

[willthames]

Some of those are ansible warnings and they are just printed out - I have no control over them.

Having said that, ansible-review is able to detect duplicate keys (as it's able to perform analysis on inventory files and many other ansible file types)

[ssbarnea]

@willthames Is something that ansible-lint does more or better than ansible-review?

Oops, missed that there is willthames/ansible-review#31 already open regarding this.

[l0b0]

This seems to be an issue still.

[peterhalasz]

It was not clear from the thread but this has been already implemented. You can use the --strict flag.
See: Code and PR