Bug 1248701 - RFE - OSEv3 needs an easy way to store secrets for external code repos
Summary: RFE - OSEv3 needs an easy way to store secrets for external code repos
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.0.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Mike Barrett
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-30 16:05 UTC by Nicholas Schuetz
Modified: 2019-10-10 10:01 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-30 18:54:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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


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