Support multi ssh-keys in git client#6776
Open
Bibisha06 wants to merge 1 commit into
Open
Conversation
Signed-off-by: Bibisha B <bibisha2006z@gmail.com>
This file contains hidden or 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
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.
What this PR does:
This PR implements support for multiple SSH keys in the Piped Git configuration. It introduces a new
sshKeyslist field to PipedGit while maintaining full backward compatibility with the existing single-key setup.Key changes:
~/.ssh/configfile that writes the legacy host entry first followed by entries in thesshKeyslist, preserving SSH's first-match-wins logic.0600permissions via a new writeSSHKeyFile helper.os.RemoveAllcall.pkg/configv1to prevent duplicate host mappings and ensure configuration integrity.Why we need it:
Some repositories may require distinct SSH keys (e.g., repository-specific deployment keys or keys across different organizations/domains) that cannot be handled by a single global SSH key.
Which issue(s) this PR fixes:
Fixes #4311
Does this PR introduce a user-facing change?: