Open grant0417 opened 1 year ago
This issue is currently awaiting triage.
If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
/sig cli
This sound like a decent issue to start with as a new contributor I feel? Could I take this up if it gets accepted by a sig?
/transfer kubectl
/assign
/triage accepted /priority backlog
Reasonable request. Thanks for offering to work on it @XDRAGON2002. Let me know if you run into issues with the printers.
@grant0417 earliest this would make it in is 1.28 so if you're time pressed you could essentially walk and build your own via
kubectl get --raw /apis
Oh interesting! No, not a major rush here. Just want to improve some of our ux but it isn't a major priority.
Thanks @eddiezane and @XDRAGON2002
Thanks @eddiezane @grant0417, have opened a PR for the same, you can have a look.
I'd like to work on this.
/assign
What would you like to be added?
Currently the
kubectl api-resources
command--output
flag only takeswide
orname
, a machine readable format such asjson
would be useful for scripting/utilizingkubectl
Why is this needed?
I am a dev at fig and help maintain the autocomplete repo, we generate completions for the
kubectl
CLI based onkubectl api-resources --output name
right now, but this lacks support for short names which are hard to parse from the human readablekubectl api-resources
, which would be easily parsed from akubectl api-resources --output json
command.This might be a much less common use case for others but it still feels useful to have machine readable output for as many
--output
flags as possible.