-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global status output / machine readable #4097
Comments
From http://docs.vagrantup.com/v2/cli/machine-readable.html:
The documentation is not correct & misleading in the presence of this issue. |
Automating code needs to know the ID of running vagrants so it can pass the ID to other commands. And the way to do that is with global-status, and it's not --machine-readable! (facepalm.jpg) |
It also makes it easier to write tutorials for people learning vagrant because you can more easily write a test that the user has done the right thing. |
Actually surprised to see docs and reality mismatch :) |
In v1.8.1 there is output for
|
Adding
--machine-readable
tovagrant global-status
returns nothing (Vagrant 1.6.2).Would be really handy to have an easy-to-parse output from this command :)
The text was updated successfully, but these errors were encountered: