15cf931d7e
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.
Team and repository tags
puppet-openstack-cookiecutter
Cookiecutter template for a compliant OpenStack puppet-modules
Installation
Install cookiecutter either from source, pip or package if it exists
Usage
There are two ways to create the boilerplate for the puppet module.
Locally
- Clone locally the puppet-openstack-cookiecutter repository.
- Run
cookiecutter /path/to/cloned/repo
Remotely (ie. using a git repo)
- Run
cookiecutter https://git.openstack.org/openstack/puppet-openstack-cookiecutter.git
What's next
Once the boilerplate created, in order to be compliant with the other modules, the files managed by msync, (or configs) needs to be in the project folder. Once synced module is ready, announce its existence to the ML, make the proper patch to openstack-infra and finally wait for the reviews to do the rest.