-
Notifications
You must be signed in to change notification settings - Fork 311
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
Generate ssh key #774
Generate ssh key #774
Conversation
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #774 +/- ##
==========================================
+ Coverage 31.93% 32.44% +0.50%
==========================================
Files 62 63 +1
Lines 4831 4931 +100
==========================================
+ Hits 1543 1600 +57
- Misses 3167 3199 +32
- Partials 121 132 +11
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would go with this approach too.
I wouldn't show any output related to SSH, I think it is an implementation detail, but we can do that later when we consolidate the ssh implementation.
That's somethign that I've been thinking about as well. We need to show output because generating those keys takes about 10 seconds. Maybe change the text to just talk about generating key pair? |
@rberrelleza yes, for now I would go with this implementation. in the future, we can abstract SSH away and don't show anything ssh related in the output |
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Thank you for your contribution. I've just checked and your commit doesn't appear to be signed-off. That's something we need before your Pull Request can be merged. Please see our contributing guide. |
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
Signed-off-by: Ramiro Berrelleza <rberrelleza@gmail.com>
This is part of #475
Proposed changes
By itself, this doesn't do anything until
remote
accepts public key authenticationI decided to create a separate key to keep it separately from existing setup. This is something we could even use later for access to other services (like buildkit). Another option is to use the users's private/public keys for this. what do you think?