Puppet module to manage VCS repositories
1b625245d6
Instead of keeping a local copy of spec_helper_acceptance.rb and requiring updates to all modules for any change, we can move it into the common helper gem and require it from there. This will make it easier to create and review changes that affect all puppet modules. Also change the Gemfile to look for the gem in the local workspace if running in a zuul environment. Change-Id: I11adccf36f9aef32a46de7179d48f6ef296771e2 |
||
---|---|---|
examples | ||
lib/puppet | ||
spec/acceptance/nodesets | ||
.gitignore | ||
.gitreview | ||
Gemfile | ||
LICENSE | ||
metadata.json | ||
Rakefile | ||
README.BZR.markdown | ||
README.CVS.markdown | ||
README.GIT.markdown | ||
README.HG.markdown | ||
README.markdown | ||
README.SVN.markdown |
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 documentation1.
More Examples
For examples you can run, see examples/svn/