Skip to content
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

Closed
grega opened this issue Jun 24, 2014 · 5 comments
Closed

Global status output / machine readable #4097

grega opened this issue Jun 24, 2014 · 5 comments

Comments

@grega
Copy link

grega commented Jun 24, 2014

Adding --machine-readable to vagrant global-status returns nothing (Vagrant 1.6.2).

Would be really handy to have an easy-to-parse output from this command :)

@aronatkins
Copy link

From http://docs.vagrantup.com/v2/cli/machine-readable.html:

Every Vagrant command accepts a --machine-readable flag which enables machine readable output mode. In this mode, the output to the terminal is replaced with machine-friendly output.

The documentation is not correct & misleading in the presence of this issue.

@f3rrix
Copy link

f3rrix commented Apr 18, 2015

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)

@amfarrell
Copy link

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.

@tuminoid
Copy link

tuminoid commented Dec 4, 2015

Actually surprised to see docs and reality mismatch :)

@tuminoid
Copy link

tuminoid commented Jan 8, 2016

In v1.8.1 there is output for --machine-readable, but output looks kind of horrible. In #6237 there is comment about upcoming work to support JSON, so I guess with this output this issue too can be closed.

1452253445,,ui,info,id
1452253445,,ui,info,name
1452253445,,ui,info,provider
1452253445,,ui,info,state
1452253445,,ui,info,directory
1452253445,,ui,info,
1452253445,,ui,info,------------------------------------------------------------------------
1452253445,,ui,info,e9bdd8e
1452253445,,ui,info,kisakone
1452253445,,ui,info,parallels
1452253445,,ui,info,running
1452253445,,ui,info,/Users/tumi/git/mine/kisakone-dev
1452253445,,ui,info,
1452253445,,ui,info,2af2ab7
1452253445,,ui,info,sfldev
1452253445,,ui,info,parallels
1452253445,,ui,info,running
1452253445,,ui,info,/Users/tumi/git/sfl/sfl-dev
1452253445,,ui,info,
1452253445,,ui,info, \nThe above shows information about all known Vagrant environments\non this machine. This data is cached and may not be completely\nup-to-date. To interact with any of the machines%!(VAGRANT_COMMA) you can go to\nthat directory and run Vagrant%!(VAGRANT_COMMA) or you can use the ID directly\nwith Vagrant commands from any directory. For example:\n"vagrant destroy 1a2b3c4d"

@ghost ghost locked and limited conversation to collaborators Apr 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants