Vagrant next release will fully support inventory changes introduced by Ansible 2.0

[Gilles Cornu]

Dear Ansiblers!

I'm very happy to announce you that the next Vagrant release will fully support Ansible 2.x inventory variables (e.g. `ansible_host` instead of `ansible_ssh_host`) and also allow to get rid of deprecation messages around the `sudo`/`become` parameters.
In order to achieve this in a backwards compatible manner, a new "compatibility_mode" option will be introduced. More details about this concept will be presented and discussed on the vagrant mailing-list. If you have time and interest on this, I would be very thankful if you can have a look and give your feedbacks.

Note: I'm not aware of any other major (breaking) change in the Ansible 2.x series that could have an impact on the Vagrant provisioners. If I missed something, please tell us!

Thank you very much in advance! Best regards,
Gilles Cornu

PS: Please don't answer to this thread, but in the vagrant mailing-list.