-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for git credential pass-through to studio. #2099
Comments
There is this feature that was added way back to support sourcing of |
The primary development scenario that we are working towards is to have the developer clone their software onto their host machine and then enter a studio from there. With that said, pulling from git from within the studio is something that you may still need to do given this scenario. For example, you may have a build tool which pulls a dependency from a private git repo which requires these credentials as part of the build process itself. I'm going to mark this as help wanted for now. I think @bdangit is on the right track with the |
I am going to close this as I .studiorc does what we need. |
Copying this from the other issue: ...in my opinion the experience (using If at all possible, authentication should just follow me in to the studio so I don't think about it. If some extra configuration is actually required (maybe my SSH key has a non-standard name or whatever), it would be nice if I got an error message that helped me figure out what to do. It's tricky since the build tool is in charge but maybe some magic could be done by wrapping |
Maybe the new secret sharing feature of studio can help? (can't find doc though) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you. |
This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details. |
As a developer, I would like to be able to access private repositories which require some form of authentication to clone and for security reasons I do not want to store the credentials within the plan itself.
See the following thread discussion on slack (hopefully it doesn't vanish into the ether): https://habitat-sh.slack.com/archives/C0VBY57UP/p1492113443402203
https://habitat-sh.slackarchive.io/general/page-100
The text was updated successfully, but these errors were encountered: