History

Tweak Ruby->Go error handling so exit codes match

In legacy Vagrant, any exception raised that's a subclass of
Vagrant::Errors::VagrantError is considered user-facing and so causes
the error message to be printed to the console and the process to use
exit code 1. Anything outside of that causes the process to use exit
code 255. (See `bin/vagrant` for the code.)

Here we mirror that behavior by treating errors that have a
LocalizedMessage as user-facing and those without as unexpected. This
allows the basic virtualbox component to pass in vagrant-spec!

2022-04-25 12:26:49 -05:00

commands

Tweak Ruby->Go error handling so exit codes match

2022-04-25 12:26:49 -05:00

communicators

Check for nil return from forwarded ports cap

2020-08-19 17:13:33 -05:00

guests

Fix guest plugin issues

2022-04-25 12:24:47 -05:00

hosts

Make myplugin have parents darwin and bsd

2022-04-25 12:24:48 -05:00

kernel_v1

Support environment variable forwarding, fixes #4131

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

kernel_v2

Allow go push plugins to use config from Vagrantfile

2022-04-25 12:26:21 -05:00

providers

Add mapper for a Class to String

2022-04-25 12:26:12 -05:00

provisioners

Set a default environment for the puppet provisioner

2022-04-25 12:24:18 -05:00

pushes

Fix local exec pushes in server mode

2022-04-25 12:26:17 -05:00

synced_folders

Use optional fields on Synced Folder instead of empty string checks

2022-04-25 12:26:44 -05:00

README.md

Return a result from an up action

2022-04-25 12:23:51 -05: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.

Generate proto

grpc_tools_ruby_protoc -I . --ruby_out=gen/plugin --grpc_out=gen/plugin ./plugin_server.proto