History

Fix Docker machines being lost in go side

By pruning machines that are in "unknown" status after each operation,
the Go code path exposed the fact that the Docker provider was not
updating the machine index during an "up" - leaving the state as
"unknown".

This is basically a bug within the Docker provider, so I think it's okay
to update the plugin code to correct this rather than working around the
issue in Go.

All we need to do is call `machine.state` instead of reaching through to
`machine.provider.state` while waiting for the container to be started.
That causes the extra logic for updating the machine index in
`machine.state` to fire.

2022-07-13 14:04:32 -05:00

commands

Use #to_proto on class match, otherwise convert

2022-07-11 15:09:46 -07: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

Remove old proto constants

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

providers

Fix Docker machines being lost in go side

2022-07-13 14:04:32 -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