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 | ||
README.BZR.markdown | ||
README.CVS.markdown | ||
README.GIT.markdown | ||
README.HG.markdown | ||
README.SVN.markdown | ||
README.markdown | ||
Rakefile | ||
metadata.json |
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.