Bug 1248701

Summary: RFE - OSEv3 needs an easy way to store secrets for external code repos
Product: OpenShift Container Platform Reporter: Nicholas Schuetz <nick>
Component: RFEAssignee: Mike Barrett <mbarrett>
Status: CLOSED NOTABUG QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.0.0CC: dmcphers, jkaur, jliggitt, jokerman, knakayam, libra-bugs, libra-onpremise-devel, mmccomas, nick
Target Milestone: ---Keywords: Question
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-30 18:54:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nicholas Schuetz 2015-07-30 16:05:02 UTC 
Description of problem:

There is not an easy way to use secrets to authenticate and pull source code from non-public code repos like github.  For instance, if a customer has an internal (and protected) git repo (like Stash).  Right now, you have to create a create secrets.json file, do some base64 encoding of the private key, and edit the build config, blah blah blah.

This leaves alot of room for human error.  We need an easy way enter and associate these secrets with external repos via the web console.

Thanks!
-Nick
Comment 2 Kenjiro Nakayama 2015-09-28 01:40:00 UTC 
This section in the docu is not enough for the explanation? 

https://docs.openshift.com/enterprise/3.0/dev_guide/builds.html#using-private-repositories-for-builds

FYI: Ben's reply in the internal thread
http://post-office.corp.redhat.com/archives/openshift-sme/2015-July/msg01740.html
Comment 4 Nicholas Schuetz 2015-09-30 18:54:00 UTC 
Good enough for me.  Thanks guys!

-Nick