Installer: Low: Support cloning via non-default SSH key
This is a valid use case for anyone who wants to use the installer via the fork method without using their default SSH key.
As mentioned in #37:
This one is related when the user has created a separate ssh key pair for use in accessing git lab. And has created an entry in the .ssh/config file like this: host betterFYI hostname source.ind.ie IdentityFile ~/.ssh/better_gitlab And then instead of doing a: git clone firstname.lastname@example.org:better/better.git you do a git clone git@betterFYI:better/better.git Now when you clone you are using the better_gitlab key pair, and not the id_rsa. Next when you run the install script, the call is back to the calling the host (source.ind.ie) directly and not using the config alias (betterFYI) anymore, and thus not getting through, since the call is now using the id_rsa key pair instead of the "better_gitlab" key pair I used in my example.
Setting as low priority as, while it’s a valid use case, there is no valid reason not to use your default identity. So this will remain a limitation for a while until we get around to implementing this support.