History

Fix Type::Booleans leaking through capabilities

We had some cases where calling a capability that returned a boolean was
not getting correctly unpacked, so instead of `true` or `false` the
capability was putting out
`VagrantPlugins::CommandServe::Type::Boolean`.

This may have been happening in _all_ cases where a boolean was returned
from a capability and we just didn't notice it yet because the return
value was always truthy.

These tweaks should help ensure that Ruby types make it out where they
are supposed to be in Args::Direct usage.

2022-07-07 11:29:50 -05:00

commands

Fix Type::Booleans leaking through capabilities

2022-07-07 11:29:50 -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

…

kernel_v2

Remove old proto constants

2022-06-27 11:26:22 -07:00

providers

Fix action hooks running twice in destroy_on_error scenarios

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

provisioners

Adjust provisioner to upload file before modifying it

2022-06-15 10:55:00 -07: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