vagrant/plugins
Peter Carrero d5c13dda64 puppet: Add "to_yaml" to facter call
The rationale here is to make it so existing Vagrantfile
configurations remain unchanged.

While benh57's solution worked for me, I had to add a
".to_yaml" to the VagrantFile line that implemented puppet.facter
and this would mean existing Vagrant configurations that use Puppet
would produce an error if that was not present.

Additionally, without this change, the Vagrant file also needed a
"require('yaml')" declaration to make the ".to_yaml" conversion
possible.
2016-04-13 16:11:25 -05:00
..
commands Merge pull request #5887 from msabramo/config.ssh.ssh_command 2015-07-09 14:24:48 -06:00
communicators kernel/v2: customizable sudo_command [GH-5573] 2015-07-09 09:30:47 -06:00
guests Merge pull request #5931 from kaorimatz/fix/guests-fedra-nmcli 2015-07-13 08:31:01 -07:00
hosts Fallback to /tmp if $TMPDIR is not set 2015-07-13 10:40:28 -04:00
kernel_v1 Change symbols inside hashes to 1.9 JSON-like syntax 2014-05-22 12:35:12 -04:00
kernel_v2 Merge branch 'filter_synced_folders' of https://github.com/maxlinc/vagrant into maxlinc-filter_synced_folders 2015-07-09 15:05:52 -06:00
providers providers/virtualbox: remove windows UNC path [GH-5933] 2015-07-13 08:38:41 -07:00
provisioners puppet: Add "to_yaml" to facter call 2016-04-13 16:11:25 -05:00
pushes push/local-exec: close temp script, fix inline [GH-5695] 2015-07-06 23:42:07 -06:00
synced_folders update to latest listen 2015-07-09 11:18:36 -06: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.