vagrant/templates
Gilles Cornu dc3b6341e2
provisioners/ansible: Check compatibility conflicts
Vagrant will verify that the current Ansible version does support the
requested compatibility mode (only applicable if not "auto", of course).

As mentioned in the documentation, there is no sanity checks between
`version` option and `compatibility_mode` option.

With this change, the host-based provisioner is also improved to
execute only once the "ansible" command (and store the gathered
information for multiple usages like version requirement and
compatibility checks). On the other hand, the guest-based provisioner
can still potentially execute "ansible" twice (once in the
AnsibleInstalled cap, and via "gather_ansible_version" function via
Base::set_compatibility_mode).
2017-09-06 17:12:40 +02:00
..
commands Convert atlas references to vagrant cloud 2017-06-23 10:01:51 -07:00
config Support warnings/errors when upgrading Vagrantfiles internally 2013-01-20 22:04:50 -05:00
guests Fetch first network device and pass to template for rendering 2017-05-10 12:44:37 -07:00
locales provisioners/ansible: Check compatibility conflicts 2017-09-06 17:12:40 +02:00
nfs Changed order of nfs exports parameters for FreeBSD 2014-07-03 11:02:06 -07:00
provisioners Support Chef Solo local + legacy modes 2016-05-19 15:27:17 +01:00
package_Vagrantfile.erb New `vagrant package` option `--vagrantfile` and changed semantics of `--include` (see CHANGELOG) 2010-09-12 23:20:13 -06:00
rgloader.rb Extra protection in the rgloader file 2013-01-31 19:54:50 -08:00