vagrant/plugins/provisioners
Brian Cain 0a6c4e2d0f
Ensure relative path for file provisioner is relative to machines cwd
Prior to this commit, if you ran Vagrant in a different current working
directory other than where a current guest machines location is, the
file provisioner would not take into account the machines local dir, and
would instead use the path where Vagrant was invoked to expand the
`source` path option for a file provisioner. This commit fixes that by
passing the root path `machine.env.cwd` when expanding the source dir.
2019-10-02 15:33:23 -07:00
..
ansible Fixes #10950: Ensure pip_install_cmd is finalized 2019-10-02 10:33:31 -07:00
cfengine #6674 CFEngine Provisioner Broken on Debian (http > https) 2015-12-16 14:25:23 +01:00
chef FreeBSD: Remove APT-ism 2019-09-17 03:58:37 -03:00
docker Reset communicator after updating user groups 2018-11-12 15:36:21 -08:00
file Ensure relative path for file provisioner is relative to machines cwd 2019-10-02 15:33:23 -07:00
puppet Fixes #8315: Properly set env variables for puppet provisioner 2018-09-18 10:09:01 -07:00
salt Merge pull request #10539 from jalandis/disable-required-install_type-salt-option-windows 2019-01-03 13:44:05 -08:00
shell Add reboot option to shell provisioner 2018-12-21 15:50:59 -08:00