Db indexing for git authorized keys #177
Merged
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
|
so it looks like my builds are failing because there was a network timeout during one of the jobs. Only that one job failed, and all the others passed. Looks like this is a common problem with ruby deps, according to Travis help docs: https://docs.travis-ci.com/user/common-build-problems/#My-builds-are-timing-out. I'm going to close and re-open the PR just to see if it will try to rebuild. |
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.
This enhancement allows for fast lookups for ssh keys for communicating with gitlab instances using git+ssh protocol.
As described in the speed up ssh operations documentation, gitlab has a feature that will allow the gitlab_shell to index authorized_keys for git+ssh connections in the database instead of the authorized_keys file. This can drastically impact the speed of ssh connections when a large number of keys or users are present.
closes #168