Add pointer for Puppet SSH approach

This commit is contained in:
Bruce Williams 2010-03-14 03:00:37 -07:00
parent 67aa190396
commit 6904cd9a71
5 changed files with 96 additions and 0 deletions

View File

@ -32,7 +32,16 @@ For a specific revision, use `revision` with a valid revisionspec
revision => 'menesis@pov.lt-20100309191856-4wmfqzc803fj300x' revision => 'menesis@pov.lt-20100309191856-4wmfqzc803fj300x'
} }
For sources that use SSH (eg, `bzr+ssh://...`, `sftp://...`)
------------------------------------------------------------
Manage your SSH keys with Puppet and use `require` in your `vcsrepo`
to ensure they are present. For more information, see the `require`
metaparameter documentation[1].
More Examples More Examples
------------- -------------
For examples you can run, see `examples/bzr/` For examples you can run, see `examples/bzr/`
[1]: http://docs.reductivelabs.com/references/stable/metaparameter.html#require

View File

@ -40,3 +40,17 @@ For a specific tag, use `revision`:
source => ":pserver:anonymous@example.com:/sources/myproj", source => ":pserver:anonymous@example.com:/sources/myproj",
revision => "SOMETAG" revision => "SOMETAG"
} }
For sources that use SSH
------------------------
Manage your SSH keys with Puppet and use `require` in your `vcsrepo`
to ensure they are present. For more information, see the `require`
metaparameter documentation[1].
More Examples
-------------
For examples you can run, see `examples/cvs/`
[1]: http://docs.reductivelabs.com/references/stable/metaparameter.html#require

View File

@ -47,3 +47,17 @@ For a specific revision (can be a commit SHA or tag):
revision => '1.1.2rc1' revision => '1.1.2rc1'
} }
For sources that use SSH (eg, `username@server:...`)
----------------------------------------------------
Manage your SSH keys with Puppet and use `require` in your `vcsrepo`
to ensure they are present. For more information, see the `require`
metaparameter documentation[1].
More Examples
-------------
For examples you can run, see `examples/git/`
[1]: http://docs.reductivelabs.com/references/stable/metaparameter.html#require

View File

@ -39,3 +39,17 @@ You can also set `revision` to a tag:
source => "http://hg.example.com/myrepo" source => "http://hg.example.com/myrepo"
revision => '1.1.2' revision => '1.1.2'
} }
For sources that use SSH (eg, `ssh://...`)
------------------------------------------
Manage your SSH keys with Puppet and use `require` in your `vcsrepo`
to ensure they are present. For more information, see the `require`
metaparameter documentation[1].
More Examples
-------------
For examples you can run, see `examples/hg/`
[1]: http://docs.reductivelabs.com/references/stable/metaparameter.html#require

View File

@ -1,2 +1,47 @@
Using vcsrepo with Subversion Using vcsrepo with Subversion
============================= =============================
To create a blank repository
----------------------------
To create a blank repository suitable for use as a central repository,
define a `vcsrepo` without a `source` or `revision`:
vcsrepo { "/path/to/repo":
ensure => present,
provider => svn
}
To checkout from a repository
-----------------------------
Provide a `source` qualified to the branch/tag you want:
vcsrepo { "/path/to/repo":
ensure => present,
provider => svn,
source => "svn://svnrepo/hello/branches/foo"
}
You can provide a specific `revision`:
vcsrepo { "/path/to/repo":
ensure => present,
provider => svn,
source => "svn://svnrepo/hello/branches/foo",
revision => '1234'
}
For sources that use SSH (eg, `svn+ssh://...`)
----------------------------------------------
Manage your SSH keys with Puppet and use `require` in your `vcsrepo`
to ensure they are present. For more information, see the `require`
metaparameter documentation[1].
More Examples
-------------
For examples you can run, see `examples/svn/`
[1]: http://docs.reductivelabs.com/references/stable/metaparameter.html#require