Red Hat Bugzilla – Bug 1615214
It does alter the object on the server when oc set env -o yaml
Last modified: 2018-10-11 03:25:05 EDT
Description of problem: `oc set env -h` says: # Output modified build config in YAML, and does not alter the object on the server oc set env bc/sample-build STORAGE_DIR=/data -o yaml But it does alter! cli l/l Version-Release number of selected component (if applicable): oc v3.11.0-0.11.0 How reproducible: always Steps to Reproduce: 1.Create app $oc new-app https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/build/tc470422/application-template-stibuild.json 2.Output modified build config in YAML $oc set env bc/ruby-sample-build -e STORAGE_DIR\=/data -o yaml 3.Check the bc $oc set env bc/ruby-sample-build --list=true # buildconfigs/ruby-sample-build EXAMPLE=sample-app FOO=foo STORAGE_DIR=/data Actual results: The env(STORAGE_DIR=/data) is in bc Expected results: The env(STORAGE_DIR=/data) should not be in bc Additional info: fyi, if oc set env bc/ruby-sample-build STORAGE_DIR=/data -o yaml --dry-run=true will not set env in bc
Origin PR: https://github.com/openshift/origin/pull/20625
Origin PR has merged. Moving to MODIFIED
verified in oc v3.11.0-0.25.0
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:2652