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.

Sign up for GitHub

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

Jump to bottom

status command should support json output #5080

Closed
redborian opened this issue Aug 14, 2019 · 1 comment · Fixed by #5611
Closed

status command should support json output #5080

redborian opened this issue Aug 14, 2019 · 1 comment · Fixed by #5611
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. ux/embedded Embedded UX blockers

Comments

@redborian
Copy link

For upstream tooling, we need JSON output for commands like minikube status.

The exact command to reproduce the issue:
minikube status

cc: @tstromberg
@tstromberg tstromberg changed the title Minikube status command should support json output status command should support json output Aug 15, 2019
@tstromberg tstromberg added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 15, 2019
@tstromberg tstromberg added the ux/embedded Embedded UX blockers label Aug 22, 2019
@tstromberg tstromberg added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Sep 20, 2019
@tstromberg
Copy link
Contributor

Seems reasonable. We'll definitely want this for implementing a future UI.

@tstromberg tstromberg mentioned this issue Oct 2, 2019
Closed
@woodcockjosh woodcockjosh mentioned this issue Oct 14, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. ux/embedded Embedded UX blockers
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add json output for status woodcockjosh/minikube
2 participants
@tstromberg @redborian