openstack/puppet-openstack-cookiecutter
Code Issues Proposed changes
Cookiecutter template for a compliant OpenStack puppet-modules
28 Commits 1 Branch 0 Tags 1.7 MiB
Puppet 39.9%
Ruby 37.5%
Shell 10.8%
Python 10.6%
Pascal 1.2%
60c3a3478a
Go to file
Yanis Guenane 60c3a3478a Handle the postgresql md5password in specs 
Current password in spec/classes/X_db_postgresql_spec.rb isn't generic,
and will cause spec to fails.
This patch aims to generate this value on the fly for the to be created
project.

Change-Id: I113e6143f4a714e079e79749b4034880e3bd1440
2015-07-10 18:07:54 +02:00
contrib Handle the postgresql md5password in specs 2015-07-10 18:07:54 +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.