Re: [kubernetes/kubernetes] jsonpath template output should be json (#16707)
Michail Kargakis
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
k8s-ci-robot
Closed #16707.
Tim Malone
/reopen
Kubernetes Prow Robot
@tdmalone: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
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.
Luis Davim
I agree this should be /reopen
Tim Malone
@mikedanese Any possibility of reopening this?
Mike Danese
Reopened #16707.
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Luis Davim
/remove-lifecycle stale
Danil Smirnov
Can we have this implemented?
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Chew Choon Keat
in the meantime...
- kubectl get no -o jsonpath="{.items}" + kubectl get no -o json | jq ".items"
Danil Smirnov
in the meantime...
- kubectl get no -o jsonpath="{.items}" + kubectl get no -o json | jq ".items"
Sorry but I don't want to add jq dependency into my container.
And jsonpath is quite different language than jq, so you can not "just change" -o jsonpath= to -o json as in your example, you have to translate the query as well.
Beck
guess i'll just move to :D
but anyway bump, it should have output as json or have at least an option to do so
AJ Escalera
+1
This would be incredibly helpful as it would allow for custom object creation without requiring external de/serialization (eg via a program written in go, java).
For example, if I wanted to grab a bunch of options in a pod or pod template and analyze them to see if I needed to update the object, it is much easier and more maintainable for automation (eg via ansible) to be written in shell and use kubectl with jsonpath, than to require the user to write a program for parsing specific objects.
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
—
Danil Smirnov
/remove-lifecycle stale
Tim Hockin
@kubernetes/sig-cli-bugs This is still an issue - jsonpath formatting for a non-primitive type is Go's weird printing syntax (blech)
Timofei Larkin
I think it's a misconception to call jsonpath an output format. It's a form of query. I should be able to do something like
k get resource --jsonpath='{.some.sub.path}' -o yaml
Andrei Belov
agree with @lllamnyp.
A good example of that would be aws-cli with both --query AND --output available.
red8888
This should at least be toggle-able. I can think of plenty of use cases where you want to parse kubectl output and send it along as structured data (json) so some other system/function.
Seems like this is designed purely for interactive use and should not be relied upon for any kind of automation? Feels kind of dumb to have to introduce an external dependency (jq) when kubectl natively supports a lot of this filtering.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are on a team that was mentioned.