Puppet module to manage VCS repositories
9263900fd8
This commit was bulk generated and pushed by the OpenDev sysadmins as a part of the Git hosting and code review systems migration detailed in these mailing list posts: http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html Attempts have been made to correct repository namespaces and hostnames based on simple pattern matching, but it's possible some were updated incorrectly or missed entirely. Please reach out to us via the contact information listed at https://opendev.org/ with any questions you may have. |
||
---|---|---|
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/