ansible: promoting warnings to errors

Question

I have some continuous integration checks which run a few ansible-playbook commands. Each playbook may be running many plays, including numerous large roles.

Every now and then, somebody introduces some change that causes a warning when ansible-playbook runs, e.g. something like this:

[WARNING]: when statements should not include jinja2 templating delimiters
such as {{ }} or {% %}. Found: "{{ some_variable}}" not in
some_result.stdout

or:

[WARNING]: Consider using unarchive module rather than running tar

or some deprecation warnings like:

[DEPRECATION WARNING]: ec2_facts is kept for backwards compatibility but usage 
is discouraged. The module documentation details page may explain more about 
this rationale.. This feature will be removed in a future release. Deprecation 
warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

and so on. Sometimes these warnings pop up when we upgrade ansible versions. Regardless of why they happen, I would really like for some way to have the ansible-playbook command fail loudly when it causes one of these warnings, instead of quietly proceeding on and having my CI check be successful. Is there any way to do this? I'm using ansible 2.4.3 currently.

I find lots of discussion about ways to hide these warnings, but haven't found anything about promoting them to hard errors.

Answer 1

I have the exact same problem. My workaround is:

• run the playbook with --check and 'tee' to a temporary file
• do some grep-magic to filter out 'WARNING]:'
• do some grep-sed-magic to filter out results that are not zero (except ok/skipped)

I know it is not ideal, so if you came with a nice solution please share :-)