Bug 1956826 - buildArgs does not work when the value is taken from a secret
Summary: buildArgs does not work when the value is taken from a secret
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Adam Kaplan
QA Contact: XiuJuan Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-04 13:45 UTC by Hongkai Liu
Modified: 2021-05-05 07:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
build pod and log (8.66 KB, application/zip)
2021-05-04 13:45 UTC, Hongkai Liu
no flags Details

Description Hongkai Liu 2021-05-04 13:45:25 UTC
Created attachment 1779380 [details]
build pod and log

Description of problem:


Version-Release number of selected component (if applicable):
oc --context build01 get clusterversion
NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.9     True        False         4d15h   Cluster version is 4.7.9

How reproducible: Always

Steps to Reproduce:
$ oc new-project hongkliu-test
$ oc create is pipeline
$ oc create secret generic build-credentials --from-literal=password=123 -n hongkliu-test
$ oc apply -f test-image.build.yaml

Actual results:
STEP 6: RUN echo -n "$user=$password=" > /tmp/password.txt
STEP 7: RUN base64 /tmp/password.txt
amFjaz09

echo amFjaz09 | base64 -d
jack==%


Expected results:
The password 123 should be passed to the build.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.