Improvement: Add support for private GitHub repos
Bug #1319604 reported by
Adrian Otto
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Solum |
Fix Released
|
Wishlist
|
Ravi Sankar Penta |
Bug Description
Currently solum only supports public git repos. Add support for private repos. Use a GitHub deploy key.
summary: |
- improvement: Add support for private GitHub repos + Improvement: Add support for private GitHub repos |
Changed in solum: | |
milestone: | 2014.1.2 → juno-1 |
Changed in solum: | |
assignee: | nobody → Ravi Sankar Penta (ravips) |
Changed in solum: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/ /help.github. com/articles/ managing- deploy- keys
A deploy key is an SSH key that is stored on the server and grants access to a single repository on GitHub. This key is attached directly to the repository instead of to a user account.
This is what can allow Solum to access GitHub. We should store our private key in barbican, and use a "barbican secret" key in order to fetch the GitHub Deploy key on-demand. The advantage of this is that all accesses are logged, and Barbican can store the secret data in encrypted format.