vagrant/plugins
Seth Vargo 9559fc549c Automatically generate a node_name for Chef
This is required because the Chef Server almost always needs a node name to
interact. This will default to the hostname, but that's always going to be
`vagrant.vm`, which will collide easily.

This generates a random hostname with `vagrant-` as the prefix and stores the
result in the machine's data directory.
2015-11-19 11:38:33 -08:00
..
commands Fix bad options 2015-11-18 15:26:45 -08:00
communicators communicators/ssh: more nil guards [GH-6225] 2015-11-18 17:32:40 -08:00
guests Fix upstart detection and event emit 2015-11-18 16:18:32 -08:00
hosts Merge pull request #6475 from nikelmwann/linux-host-use-xfreerdp 2015-11-18 15:12:47 -08:00
kernel_v1 Change symbols inside hashes to 1.9 JSON-like syntax 2014-05-22 12:35:12 -04:00
kernel_v2 Merge pull request #6150 from pwnall/patch-2 2015-11-18 12:04:52 -08:00
providers Merge pull request #6552 from mitchellh/f-cache-vbox 2015-11-19 11:20:09 -08:00
provisioners Automatically generate a node_name for Chef 2015-11-19 11:38:33 -08:00
pushes push/heroku: use correct current branch [GH-6123] 2015-11-19 11:17:48 -08:00
synced_folders Merge pull request #6232 from mirthy/windows7-hostinfo 2015-11-18 13:11:10 -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.