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 <https://groups.google.com/d/msg/vagrant-up/ilrun_TouSc/j2aFDR4qAgAJ>. 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. <https://groups.google.com/d/msg/vagrant-up/ilrun_TouSc/j2aFDR4qAgAJ> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/9c990147-9e8a-4bd1-82a5-078b80754673%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
