vagrant/plugins/provisioners
Andreas Olsson f6a9dcdd6f Catch pip_args in FreeBSD's and SUSE's ansible_install
While neither the FreeBSD provisioner nor the SUSE provisioner support
installing Ansible using pip their ansible_install methods still get
called with that fourth argument. The result being these errors when
Vagrant tries to install Ansible.

    /opt/vagrant/embedded/gems/gems/vagrant-1.9.5/plugins/provisioners/ansible/cap/guest/freebsd/ansible_install.rb:10:in `ansible_install': wrong number of arguments (4 for 3) (ArgumentError)
    /opt/vagrant/embedded/gems/gems/vagrant-1.9.5/plugins/provisioners/ansible/cap/guest/suse/ansible_install.rb:9:in `ansible_install': wrong number of arguments (4 for 3) (ArgumentError)

The Arch provider, it too without pip support, already catches the
pip_args argument this way.
2017-06-14 21:01:44 +02:00
..
ansible Catch pip_args in FreeBSD's and SUSE's ansible_install 2017-06-14 21:01:44 +02:00
cfengine #6674 CFEngine Provisioner Broken on Debian (http > https) 2015-12-16 14:25:23 +01:00
chef Add chef_install(ed?) guest capability for freebsd 2017-04-04 22:10:02 -07:00
docker Add /bin/docker to path list for installation verification 2017-03-20 11:38:44 -07:00
file provisioners/file: validate source relative to Vagrantfile path 2015-07-06 14:22:00 -06:00
puppet Default the puppet config environment variables to an empty hash 2016-10-27 15:14:13 -07:00
salt update latest salt minion version for windows 2017-04-13 12:36:45 -07:00
shell Fix shell provisioner to execute batch files correctly 2017-04-28 15:05:08 -07:00