-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Comments
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 |
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. |
@fabianofranz We've been discussing some changes here https://github.com/abstractj/origin/commit/88bf1621ec7b4ea8e31f1bedd4c4336c6969f3a1#commitcomment-22954041. Sharing just in case. |
@fabianofranz fyi I reassigned this to Juan, because his solution (juanvallejo@875b22c) is way ahead than mine |
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
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.
The text was updated successfully, but these errors were encountered: