-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add json output for status #5611
Add json output for status #5611
Conversation
Hi @woodcockjosh. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Can one of the admins verify this patch? |
/assign @medyagh |
Travis tests have failedHey @woodcockjosh, 1st Buildmake test
TravisBuddy Request Identifier: b27b8ce0-edd1-11e9-b065-29d3c1d45cd6 |
ea6a7b1
to
d33f3b2
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: woodcockjosh The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #5611 +/- ##
==========================================
- Coverage 37.23% 37.17% -0.07%
==========================================
Files 103 103
Lines 7528 7546 +18
==========================================
+ Hits 2803 2805 +2
- Misses 4352 4368 +16
Partials 373 373
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, just some minor naming nits. Thank you for writing an integration test!
/ok-to-test |
@tstromberg I please check this update. From my perspective the current output doesn't make sense.
For this reason I think it makes sense to modify the current output while adding json output. The JSON output needs to be simple and doesn't need to have user messages. We also want the json output to be somewhat congruent with the default output. I have separated the kubeconfig status from the warning message in case the kubeconfig is misconfigured. I think this is cleaner and less confusing. |
PR looks good, but the status integration test is failing:
NOTE: This may be an unrelated error and fixed by #5649 |
a34b498
to
c436aa0
Compare
@tstromberg works on my machine :-D make integration -e TEST_ARGS="-test.parallel=1 -test.run TestFunctional/parallel/StatusCmd --profile=minikube --cleanup=false"
I did rebase off master but I'm not sure it helped |
c436aa0
to
144654e
Compare
Looks good. Thank you! |
Adds json output for
minikube status
commandAdds shorthand argument for format option
Before
Command:
Output:
After
Adds json output
Command:
Output:
Adds shorthand for format option
Command:
Output:
Output and Format options cannot both be used at the same time
Command:
minikube status -o json -f "hello"
Output:
Fixes #5080