History

smoyer 3964298504 This was introduced in 1.4.1 with d26c147.

This PR sets the active hostname back to the name specified in the Vagrantfile (fqdn) and updates the unit tests.

Setting it to the short name causes loads of problems while configuring the system. I've had issues with sudoers hostname matching, Weblogic certificate generation and a few others. Even if I changed all of the Chef recipes, the fqdn is set in /etc/sysconfig/network so the active hostname will switch to the fqdn after a reboot.

2014-01-08 17:49:54 -05:00

commands

commands/plugin: vagrant plugin install can accept multiple

2014-01-07 14:17:48 -08:00

communicators/ssh

communicators/ssh: if insert_key is false, don't insert a key

2014-01-03 11:29:44 -08:00

guests

This was introduced in 1.4.1 with d26c147.

2014-01-08 17:49:54 -05:00

hosts

hosts/*: proper detect API

2014-01-07 21:18:36 -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: a host always exists, remove dumb check

2014-01-07 21:20:28 -08:00

providers/virtualbox

providers/virtualbox: don't error when intnet set to "true" [GH-2751]

2014-01-03 08:31:14 -08:00

provisioners

provisioners/chef-solo: Fix copy&paste "Puppet" from a deprecation message

2014-01-08 13:27:35 -03:00

synced_folders/nfs

hosts/bsd: convert to new style

2014-01-07 20:39:24 -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.