ignore build version on bc update if version is older than existing value#9568
Conversation
|
[test] |
bparees
force-pushed
the
ignore_build_version
branch
from
e605d76 to
5f909d2
Compare
|
infrastructure flake. [test] |
|
Evaluated for origin test up to 5f909d2 |
|
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/5436/) |
|
LGTM |
|
[merge] Ben Parees | OpenShift
|
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/5438/) (Image: devenv-rhel7_4467) |
|
Evaluated for origin merge up to 5f909d2 |
3 participants
fixes #9301
@Kargakis @csrwng ptal. I know the "right" fix here is to change the default bc resource to ignore status updates, and introduce a new resource that accepts status updates (and possibly spec updates) and use that from our clone/instantiate logic when updating a BC, but this seems simpler and sufficient for now. I can't think of any reason we'd want to let someone update a BC to make the status older than the current value (especially if the right fix wouldn't let them update the BC status at all anyway).