openstack/puppet-openstack-cookiecutter
Code Issues Proposed changes
Cookiecutter template for a compliant OpenStack puppet-modules
148 Commits 1 Branch 0 Tags 1.7 MiB
Puppet 39.9%
Ruby 37.5%
Shell 10.8%
Python 10.6%
Pascal 1.2%
9829629627
Go to file
ZhongShengping 9829629627 Update LICENSE 
In order to better understand the LICENSE

Change-Id: I7ada62e76042bf12c1733fc1571dd21461bc6095
Depends-On: Id1a39a34278b9727cd083d89a63ea31342a28fee
2018-04-06 20:20:32 +08:00
contrib Handle unset git information 2017-11-03 16:55:52 -06:00
puppet-{{cookiecutter.project_name}} Update LICENSE 2018-04-06 20:20:32 +08:00
.gitignore Add .gitignore and cleanup in functions 2016-08-03 17:46:40 -04:00
.gitreview Add .gitreview configuration 2015-06-26 18:03:07 +02:00
.zuul.yaml Switch jobs to Zuul v3 2018-02-13 00:28:01 +00:00
bindep.txt Move other-requirements.txt to bindep.txt 2016-08-12 21:09:45 +02:00
cookiecutter.json cookiecutter.json: bump to 2016 2016-01-02 08:06:56 -05:00
functions Add .gitignore and cleanup in functions 2016-08-03 17:46:40 -04:00
LICENSE Initial commit 2015-05-21 21:11:28 +02:00
README.md Update to the latest address in README 2017-09-21 12:02:40 +08:00
run_beaker_tests.sh Add CI scripts 2016-07-26 13:28:09 -04:00
run_lint_tests.sh Add CI scripts 2016-07-26 13:28:09 -04:00
run_syntax_tests.sh run_syntax: use PUPPET_MAJOR_VERSION 2016-07-26 14:57:59 -04:00
run_unit_tests.sh Support puppet 4.8 and latest for libraries unit test 2018-03-27 16:01:59 +08:00

README.md

Team and repository tags

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

  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://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.