You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Todd Mitton (JIRA)" <ji...@apache.org> on 2017/07/08 02:08:00 UTC
[jira] [Created] (MYNEWT-805) Better support for private repos
Todd Mitton created MYNEWT-805:
----------------------------------
Summary: Better support for private repos
Key: MYNEWT-805
URL: https://issues.apache.org/jira/browse/MYNEWT-805
Project: Mynewt
Issue Type: Improvement
Security Level: Public (Viewable by anyone)
Components: Newt
Reporter: Todd Mitton
Assignee: Todd Mitton
Priority: Minor
A password or personal access token must be specified in project.yml for `newt install` to access a private repo. This makes it hard to use private repos in automated environments because it would require checking in the clear text password/token.
We should add support for getting the password/token from an env variables. CI systems like jenkins, travis, etc. securely store secrets and make them available to builds through env variables.
Even better then env variables is to use ssh instead of https. Private repos can be accessed via ssh, and newt can simply use the local ssh agent when accessing the private repo.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)