Puppet module to manage VCS repositories
Go to file
OpenDev Sysadmins 9263900fd8 OpenDev Migration Patch
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.
2019-04-19 19:25:35 +00:00
examples Make Puppet DSL compliant with the style guides and puppet lint. 2012-03-11 21:10:08 +00:00
lib/puppet Checkout local revision if not tag/remote branch. 2012-12-21 01:08:02 +00:00
spec/acceptance/nodesets Depend on helper gem for spec_helper_acceptance 2017-08-18 10:41:45 +02:00
.gitignore Add Gemfile and puppet 4 checks 2015-08-14 11:46:56 -07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:25:35 +00:00
Gemfile Update Gemfile for Zuulv3 2018-07-12 09:57:46 +02:00
LICENSE Add GPL license (from Puppet core) 2010-03-14 03:24:15 -07:00
README.BZR.markdown Tweak markup 2010-03-14 03:08:03 -07:00
README.CVS.markdown Add pointer for Puppet SSH approach 2010-03-14 03:00:37 -07:00
README.GIT.markdown (#13062) Added clarification that 'revision' can also be used for branches. 2012-04-05 14:54:40 +01:00
README.HG.markdown Tweak markup 2010-03-14 03:08:03 -07:00
README.SVN.markdown Add pointer for Puppet SSH approach 2010-03-14 03:00:37 -07:00
README.markdown Convert bare repos to working copy repos and vice-versa 2010-03-13 00:00:11 -08:00
Rakefile Add Gemfile and puppet 4 checks 2015-08-14 11:46:56 -07:00
metadata.json Replace openstack.org git:// URLs with https:// 2019-03-24 20:35:47 +00:00

README.markdown

vcsrepo

Purpose

This provides a single type, vcsrepo.

This type can be used to describe:

  • A working copy checked out from a (remote or local) source, at an arbitrary revision
  • A "blank" working copy not associated with a source (when it makes sense for the VCS being used)
  • A "blank" central repository (when the distinction makes sense for the VCS being used)

Supported Version Control Systems

This module supports a wide range of VCS types, each represented by a separate provider.

For information on how to use this module with a specific VCS, see README.<VCS>.markdown.

License

See LICENSE.