-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Better 'oc run' validations #11635
Better 'oc run' validations #11635
Conversation
[test] |
@openshift/cli-review |
Evaluated for origin test up to 23f62eb |
I'm still curious what data flow led to the args being used as a selector and all-namespaces being queried. |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10766/) (Base Commit: 0403599) |
@liggitt I didn't dig too deep, but I believe it's related to calling |
@liggitt because it only happens with |
[merge] |
Evaluated for origin merge up to 23f62eb |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10766/) (Base Commit: 8b2d509) (Image: devenv-rhel7_5278) |
Fixes #11605
Upstream PR: kubernetes/kubernetes#35732
Adds more validations to flags that must be mutually exclusive in
oc run
. For example,--dry-run
must not be used with--attach
,--stdin
, or--tty
, that doesn't make sense.