4e451c6e99
Before this change, the detection of a non-existing path on the guest machine was considered as an error and lead to interrupt the current vagrant action. This was actually a mistake to do so, since the config checks are performed before many other vagrant actions than `provision`. The config.validate phase is also intended to primarily check the options sanity, but it cannot be too strict with the guest state (which can easily get "out of automatic control"). With this change, we still apply these checks (when possible), but only warn about possible configuration problems. This way, the subsequent statements will happen anyway (e.g. ansible commands will be executed, vagrant machine will be destroyed, etc.) |
||
|---|---|---|
| .. | ||
| commands | ||
| communicators | ||
| guests | ||
| hosts | ||
| kernel_v1 | ||
| kernel_v2 | ||
| providers | ||
| provisioners | ||
| pushes | ||
| synced_folders | ||
| 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.