vagrant/plugins/provisioners
James Shubin d4c76d1bcf Do not prepend default path because it can override modules.
It is common for Puppet to manage itself. If the puppet code you are
deploying pushes files to /etc/puppet/modules/, then prepending this
path can break deployment because it will override the module path if
the deployment code is changing. There is no good reason to include this
path. Puppet has built in defaults for this reason.
2013-12-17 14:29:54 -05:00
..
ansible Add ability to use Ansible groups in generated inventory. Fixes #2551. 2013-12-08 23:08:03 -08:00
cfengine add cfengine provisioner suse install support 2013-09-25 20:29:25 -05:00
chef provisioners/chef: fix node/client deletion when node_name is not set [GH-2345] 2013-12-13 00:51:22 -03:00
docker provisioners/docker: Display warning in case a version get specified on the Vagrantfile and the guest is a RedHat-ian guest [GH-2649] 2013-12-13 23:06:20 -02:00
file provisioners/all: report proper invalid keys [GH-2117] 2013-09-04 16:57:15 -07:00
puppet Do not prepend default path because it can override modules. 2013-12-17 14:29:54 -05:00
salt salt-bootstrap.sh: options are only allowed before install arguments 2013-11-29 15:52:12 +01:00
shell provisioners/shell: array args properly work 2013-12-06 11:28:32 -08:00