vagrant/plugins/providers/virtualbox/action
Mitchell Hashimoto e0ec679838 `vagrant ssh` with full console works with new provider.
This works by now calling the `:ssh` action on the provider. This action
is allowed to do whatever it pleases, but should at some point probably
call the `SSHExec` built-in middleware.

The `SSHExec` built-in middleware was added. This uses the information
returned by `Machine#ssh_info` and uses the `Vagrant::Util::SSH` helper
to exec into the remote machine. The provider should do any work upfront
in verifying that the machine is ready to be SSHed into.
2012-08-05 13:45:24 -07:00
..
check_accessible.rb Building up the `destroy` action again using new provider API. 2012-07-26 22:39:27 -07:00
check_created.rb `vagrant ssh` with full console works with new provider. 2012-08-05 13:45:24 -07:00
check_running.rb `vagrant ssh` with full console works with new provider. 2012-08-05 13:45:24 -07:00
check_virtualbox.rb Building up the `destroy` action again using new provider API. 2012-07-26 22:39:27 -07:00
created.rb The `Call` built-in middleware allows for conditional MW sequences. 2012-07-26 23:56:47 -07:00
destroy_confirm.rb Clean up the actions a bit, move logic into actual middleware. 2012-07-28 19:58:10 -07:00
discard_state.rb Expose the provider via the machine object. 2012-08-04 11:16:31 -07:00
halt.rb Expose the provider via the machine object. 2012-08-04 11:16:31 -07:00
message_not_created.rb Start moving the halt commands over to the new provider interface 2012-07-28 10:43:16 -07:00
message_will_not_destroy.rb Clean up the actions a bit, move logic into actual middleware. 2012-07-28 19:58:10 -07:00