History

Make start action run provisioners if VM is running

Previously, there was no one gesture that would start a VM if it was not
running and run the appropriate provisioners regardless of its original
state. `vagrant up` did nothing if the VM was running, while
`vagrant provision` did nothing if the VM was not running.

Change the semantics of `vagrant up`, via the start actions of the providers,
to go through the provisioning logic even if the VM is already running.
The semantics of `run: "once"` vs `run: "always"` are respected.

Tested with the VirtualBox provider but not the others.

Resolves #4421

2016-05-27 19:00:33 -04:00

commands

Merge pull request #7059 from markpeek/markpeek-no-provision-on-resume

2016-05-27 17:07:41 -04:00

communicators

powershell and cmd calls should use commnand_executor to reuse oprn winrm shell

2016-01-27 11:59:10 -08:00

guests

Do not return an error if ifdown fails

2016-03-20 18:21:03 +02:00

hosts

Merge pull request #6602 from mitchellh/sethvargo/darwin_rdp_info

2016-02-03 10:08:18 -05:00

kernel_v1

Support environment variable forwarding, fixes #4131

2015-11-19 16:25:54 -08:00

kernel_v2

core: avoid crash case with nil [GH-6730]

2015-12-24 12:38:14 -08:00

providers

Make start action run provisioners if VM is running

2016-05-27 19:00:33 -04:00

provisioners

Trailing comma

2016-05-19 11:35:53 -04:00

pushes

Use a hash for directory lookups

2016-03-17 20:48:08 -05:00

synced_folders

Fix for problem where the host_info.ps1 script returns a string instead of a list of IPs

2015-12-17 14:40:50 -06:00

README.md

…

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.