Skip to content

oc policy can-i --list output is not parser friendly. #11147

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

Closed
pruan-rht opened this issue Sep 28, 2016 · 4 comments · Fixed by #15125
Closed

oc policy can-i --list output is not parser friendly. #11147

pruan-rht opened this issue Sep 28, 2016 · 4 comments · Fixed by #15125

Comments

@pruan-rht
Copy link
Member

oc policy can-i --list output is not parser friendly due to the lack of --output=format support

Version

oc v1.3.0-rc1+ea6ca28

Steps To Reproduce

oc policy can-i --list

Current Result

not parser friendly

Expected Result

parser friendly.

@fabianofranz
Copy link
Member

Hey @liggitt @deads2k, @abstractj is taking this one. Which output formats would you expect to have here? If the entries directly reflects single API objects then I'd say all output formats we have in get probably apply; otherwise maybe just json and yaml?

@deads2k
Copy link
Contributor

deads2k commented Jun 27, 2017

It doesn't have a name with the object comes back. Or at least not a meaningful one. Otherwise, it is a normal API object.

@abstractj
Copy link

@abstractj abstractj assigned juanvallejo and unassigned abstractj Jul 10, 2017
@abstractj
Copy link

@fabianofranz fyi I reassigned this to Juan, because his solution (juanvallejo@875b22c) is way ahead than mine

@abstractj abstractj self-assigned this Jul 21, 2017
openshift-merge-robot added a commit that referenced this issue Aug 2, 2017
Automatic merge from submit-queue (batch tested with PRs 15512, 15582, 15125, 15590, 15593)

oc policy can-i --list output is not parser friendly

@fabianofranz this fixes #11147 is just a rebase from the changes that @juanvallejo made. 
He pretty much did all the hard work on it.

fixes #11147
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants