Add support for specifying a SSH key per git repository about r10k HOT 5 CLOSED

👍 for this behavior. However the last time I played with Github deploy keys I think there had to be some special environment variable magic to do this on a per-repo basis.

In addition this would need to be done for the Puppetfile as well as top level sources, right?

from r10k.

Can't this be managed using an SSH config file? Does it make sense for it
to be managed by r10k?

Greg

On May 28, 2013, at 12:04 AM, Adrien Thebo [email protected] wrote:

[image: 👍] for this behavior. However the last time I played with Github
deploy keys I think there had to be some special environment variable magic
to do this on a per-repo basis.

In addition this would need to be done for the Puppetfile as well as top
level sources, right?

—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/37#issuecomment-18529833
.

from r10k.

Ancillas: I think maybe your approach is better. It may be out of r10k's area of responsibility.

For instance, sharing the Puppetfile between puppet masters and developers, presents problems if it contains sshkey_paths to keys, which may not exist everywhere, and r10k shouldn't generate keys.

from r10k.

@larstobi to follow up on this do you think this sort of functionality is still needed, or can we close this issue out?

from r10k.

@adrienthebo yes, I think this functionality is better served by an SSH config file, as @Ancillas suggested.

from r10k.