vagrant/plugins/commands
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
..
box Automatically upgrade the boxes all over. 2012-07-11 18:36:23 -07:00
destroy Destroy sequence asks the user for confirmation. 2012-07-27 19:29:40 -07:00
gem Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
halt Start moving the halt commands over to the new provider interface 2012-07-28 10:43:16 -07:00
init Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
package Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
provision Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
reload Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
resume Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
ssh `vagrant ssh` with full console works with new provider. 2012-08-05 13:45:24 -07:00
ssh_config Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
status Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
suspend Move command base class to a plugin component 2012-06-26 16:18:02 -07:00
up Move command base class to a plugin component 2012-06-26 16:18:02 -07:00