Skip to content
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

Closed
rhass opened this issue Apr 13, 2017 · 9 comments
Closed

Add support for git credential pass-through to studio. #2099

rhass opened this issue Apr 13, 2017 · 9 comments
Labels
Focus: Studio Related to the Habitat Studio (core/hab-studio) component Stale
Milestone

Comments

@rhass
Copy link
Contributor

rhass commented Apr 13, 2017

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

@rhass rhass added this to the Pokemon Village milestone Apr 13, 2017
@bdangit
Copy link
Contributor

bdangit commented Apr 15, 2017

There is this feature that was added way back to support sourcing of .studiorc files if it exists. When you enter the studio, Hab would automatically source it. You could potentially place any git creds like tokens and/or any other secrets that need to get passed.

@reset reset modified the milestones: Pokemon Village, Help Wanted Apr 19, 2017
@reset reset added the Studio label Apr 19, 2017
@reset
Copy link
Collaborator

reset commented Apr 19, 2017

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 .studiorc file. If this works well we should promote this in the docs and ensure there's a global .studiorc which would prevent you from needing to create one for each software project to get common credentials such as these into your studios.

@rhass
Copy link
Contributor Author

rhass commented May 9, 2017

I am going to close this as I .studiorc does what we need.

@danielsdeleo
Copy link

Copying this from the other issue:

...in my opinion the experience (using .studiorc for this functionality) falls short of hab's standards. The way it's done now is referenced in this documentation issue: #3145 but it seems silly for everyone to need to cargo-cult that code around.

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 git clone and annotating the error message in some way.

@rsertelon
Copy link
Contributor

Maybe the new secret sharing feature of studio can help? (can't find doc though)

@stale
Copy link

stale bot commented Apr 3, 2020

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.

@stale stale bot added the Stale label Apr 3, 2020
@christophermaier christophermaier added Focus: Studio Related to the Habitat Studio (core/hab-studio) component and removed A-studio labels Jul 24, 2020
@stale stale bot removed the Stale label Jul 24, 2020
@stale
Copy link

stale bot commented Jul 26, 2021

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.

@stale stale bot added the Stale label Jul 26, 2021
@stale
Copy link

stale bot commented Aug 30, 2021

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.

@stale stale bot closed this as completed Aug 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Focus: Studio Related to the Habitat Studio (core/hab-studio) component Stale
Projects
None yet
Development

No branches or pull requests

8 participants