documentation for vagrant reload is misleading

[mguterl]

http://vagrantup.com/docs/provisioners/chef_solo.html

Once enabled, if you are building a VM from scratch, run vagrant up and provisioning will automatically occur. If you already have a running VM and don’t want to rebuild everything from scratch, run vagrant reload and provisioning will automatically occur.

The second sentence leads me to believe that vagrant reload will just attempt to connect to the instance and perform provisioning. However, it seems to force shutdown the VM, start it back up, connect, and then provision. Should the documentation be made more explicit?

Is it possible to get a vagrant provision command to simply connect and execute chef-solo? Does that even make sense to do? I'm new to Vagrant Chef, but I think the whole idempotent aspect of Chef would make this command useful.

[mitchellh]

mguterl,

I'll fix the wording on the description. As for the vagrant provision command: Yes, we plan on making such a thing. :) I'll be sure to keep this issue up to date on that.

Mitchell

[mitchellh]

mguterl,

I've fixed the documentation (finally): http://github.com/mitchellh/vagrant/commit/b70c7386a5b78d41ec346e488eb1b7fa81a68c65

The vagrant provision command is still a feature request but it is planned.

Mitchell

[mitchellh]

Closing this. vagrant provision was added awhile ago.