Make it possible to provision private ssh key as well #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ioning private keys as well
…er}/.ssh/id_rsa private key
…h refuses to use it
… when there are users without a private key on s3
* upstream/master: Update README.md Update README.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Sometimes you want a provisioned user to have a private ssh key as well.
For example, our usecase is that we provision a user for our CI setup. When the instance is up and the users are installed, it is automatically added as slave to our jenkins setup. Since this slave has to checkout private git repositories, (not as start of the task, but as composer within the build process) it needs a private key.
Adding the private key is as simple as uploading a file to the keys bucket in the format: [email protected]
Cheers,