Github user JonZeolla commented on the issue:
https://github.com/apache/incubator-metron/pull/219
I agree. There are definite benefits to doing an upgrade to Ansible
(whether to 2.1 or 2.2). One of many would be the ability to use the [debug
feature](https://docs.ansible.com/ansible/playbooks_debugger.html) for
troubleshooting. I validated that there is pretty widespread support for both
2.1 and 2.2. Specifically, I quickly looked at:
* [brew](http://braumeister.org/formula/ansible)
* pip (via `pip install ansible==`)
* [apt-get](https://launchpad.net/~ansible/+archive/ubuntu/ansible) for
Ubuntu (and probably others)
* yum (via `yum list ansible` with `epel` configured)
That makes me think it may be more worthwhile to jump to 2.2 instead of
2.1, but I'm mostly indifferent.
Is there a large emphasis on having backwards compatible playbooks?
Personally I'm not so concerned about that, as long as we do a good job
documenting and **announcing** the upgrade, but I'd be interested to see in
what situations that's important.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
