You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using oc status, there are failures that have common responses. Things like "your build failed, would you like to look at logs with oc build-logs builds/foo or retry with oc start-build bc/bar? Similar help can be provided for failed deployments, service accounts with missing secrets, a stub for emptyDir volumes, etc. Sometimes that level of detail is annoying, but a flag to turn it on would be nice.
Definitely a lot of value. Probably need to break it into a card and
brainstorm some ideas and get some feedback. I'd like to be able to
resolve SME questions so they stop asking them.
We also need to figure out how the UI does the same thing, to keep rough
parity (not exact parity.
When using oc status, there are failures that have common responses. Things
like "your build failed, would you like to look at logs with oc build-logs
builds/foo or retry with oc start-build bc/bar? Similar help can be
provided for failed deployments, service accounts with missing secrets, a
stub for emptyDir volumes, etc. Sometimes that level of detail is annoying,
but a flag to turn it on would be nice.
When using
oc status
, there are failures that have common responses. Things like "your build failed, would you like to look at logs withoc build-logs builds/foo
or retry withoc start-build bc/bar
? Similar help can be provided for failed deployments, service accounts with missing secrets, a stub for emptyDir volumes, etc. Sometimes that level of detail is annoying, but a flag to turn it on would be nice.@smarterclayton @fabianofranz what do you think?
The text was updated successfully, but these errors were encountered: