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
make oc status output describeable #3687
Conversation
@smarterclayton opinions? |
adding the bc name is kind of ugly. |
If you looked at |
Yeah, but if I saw something ugly I probably wouldn't know it other. When On Mon, Jul 13, 2015 at 2:39 PM, David Eads notifications@github.com
Clayton Coleman | Lead Engineer, OpenShift |
da6fb58
to
f3fb1d1
Compare
Updated example with "built by " line. I think a lot of the uglyness is from the wrapping of the image source line, but at 120 characters that's going to happen pretty often. Tangentially related: should we warn if two BCs push to the same ISTag? |
f3fb1d1
to
f8b82ed
Compare
Is it still ugly? If so, would removing the built-by line be sufficient? What I put the bc at the end of the build line |
How about:
|
I'm not totally in love with that, but it does reduce the number of extra lines |
56a454e
to
2895028
Compare
Updated code and description to match your previous comment. |
LGTM [merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_origin/2799/) (Image: devenv-fedora_2039) |
[Test]ing while waiting on the merge queue |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/3695/) |
data race flake that was fixed [merge] |
ea68537
to
7cdc994
Compare
Evaluated for origin up to 7cdc994 |
Merged by openshift-bot
Updates
oc status
output to make it possible to copy and paste names directly intooc describe
. This way, if a new user wants more details,oc describe
arguments can be directly copied and pasted.It also makes the connections between different types very clear to advanced users. "Is this a bc, dc, or is?" will never be an issue.