haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
vagrant/plugins
History
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
..
commands commands/ssh: use proper variable 2013-12-13 22:32:01 -08:00
communicators/ssh communicators/ssh: add -E to sudo to preserve env 2013-12-03 12:07:14 -08:00
guests guests/redhat: Don't error if ifdown fails [GH-2614] 2013-12-10 20:04:36 +00:00
hosts hosts/bsd: check for exports file issues prior to exporting NFS 2013-12-13 22:14:13 -08:00
kernel_v1 kernel_v1: don't upgrade "max_tries" and "timeout" because they're gone 2013-09-02 09:09:39 -07:00
kernel_v2 kernel/v2: fix validation on checksum types 2013-12-03 18:46:22 -08:00
providers/virtualbox providers/virtualbox: don't clear /etc/exports on BSDs for NFS [GH-2645] 2013-12-13 22:03:14 -08:00
provisioners Do not prepend default path because it can override modules. 2013-12-17 14:29:54 -05:00
synced_folders/nfs providers/virtualbox: don't clear /etc/exports on BSDs for NFS [GH-2645] 2013-12-13 22:03:14 -08:00
README.md Add README to plugin directory 2012-04-18 17:48:06 -07:00

README.md

Vagrant Core Plugins

These are plugins that ship with Vagrant. Vagrant core uses its own plugin system to power a lot of the core pieces that ship with Vagrant. Each plugin will have its own README which explains its specific role.