This module configures a sane configurable ~/.ssh/config for several users.
The main goal is to have Host aliases with different ssh keypairs working like this:
http://blog.firmhouse.com/configuring-multiple-private-ssh-deploy-keys-in-jenkins-for-github-com
If you have several private repos in github.com and you want to have a privilege seperation (no global read-only user for all repositories), you can easily add a separate keypair per node/node role/profile like this:
Currently, only inserting remote hosts to a ssh user config is supported.
This done like this:
# first remote host: github.com
sshuserconfig::remotehost { 'github_for_awesome_repo1' :
unix_user => 'jenkins',
remote_hostname => 'github.com',
remote_username => 'git',
private_key_content => "some privkey content\n",
public_key_content => "some pubkey content\n",
}
# second remote host: github.com with a another key
sshuserconfig::remotehost { 'github_for_awesome_repo2' :
unix_user => 'jenkins',
remote_hostname => 'bitbucket.com',
remote_username => 'git',
private_key_content => "some privkey content2\n",
public_key_content => "some pubkey content2\n",
}
This generate a ~/.ssh/config file with two SSH Host' directives.
Now you can use a git-remote like this (as user 'jenkins'):
$ git clone git@github_for_awesome_repo1:s0enke/some_repo
$ git clone git@github_for_awesome_repo2:s0enke/some_repo_with_other_ssh_key
List supported platforms and module dependencies here
List and explain the contained manifests here
Everything you need to know about testing this module is explained in
TESTING.md.
Author:
- Ole Michaelis ([email protected])
- Soenke Ruempler ([email protected])
- Mathias Lafeldt ([email protected])
Copyright:: 2013, Jimdo GmbH
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.