openstack/puppet-openstack-cookiecutter
Code Issues Proposed changes
Cookiecutter template for a compliant OpenStack puppet-modules
26 Commits 1 Branch 0 Tags 1.7 MiB
Puppet 40%
Ruby 37.5%
Shell 10.8%
Python 10.5%
Pascal 1.2%
033f4e7c70
Go to file
Yanis Guenane 033f4e7c70 Update templates to reflect various changes 
Update the cookiecutter templates to reflect various changes :

  * Move to openstack/ scope
  * More up to date metadata.json (operatingsystem_support)
  * Fix white space
  * Fix README naming and links
  * Remove duplicated CHANGELOG

Change-Id: I520d60952f93a226a318465ec79567662274efde
2015-06-30 13:00:24 +02:00
puppet-{{cookiecutter.project_name}} Update templates to reflect various changes 2015-06-30 13:00:24 +02:00
.gitreview Add .gitreview configuration 2015-06-26 18:03:07 +02:00
cookiecutter.json config: Add a central date place (for License) 2015-05-21 23:21:41 -07:00
LICENSE Initial commit 2015-05-21 21:11:28 +02:00
README.md Update templates to reflect various changes 2015-06-30 13:00:24 +02:00

README.md

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

  1. Clone locally the puppet-openstack-cookiecutter repository.
  2. Run cookiecutter /path/to/cloned/repo

Remotely (ie. using a git repo)

  1. Run cookiecutter https://github.com/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.