openstack/puppet-openstack-cookiecutter
Code Issues Proposed changes
Cookiecutter template for a compliant OpenStack puppet-modules
220 Commits 1 Branch 0 Tags 1.7 MiB
Puppet 39.9%
Ruby 37.5%
Shell 10.8%
Python 10.6%
Pascal 1.2%
980b5b9300
Go to file
Tobias Urdin 980b5b9300 Update Puppet requirement to >= 6.0.0 
Change-Id: I3cf71a5ca43e6913c85e2f5256d197d85c120505
2020-06-01 08:22:55 +00:00
contrib Fix cookiecutter 2020-04-03 02:13:42 +02:00
puppet-{{cookiecutter.project_name}} Update Puppet requirement to >= 6.0.0 2020-06-01 08:22:55 +00:00
.gitignore Dissuade .gitignore references to personal tools 2018-10-05 18:27:10 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:29:14 +00: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 Fix cookiecutter 2020-04-03 02:13:42 +02:00
LICENSE Initial commit 2015-05-21 21:11:28 +02:00
README.md Fix Repository 2019-04-21 07:25:49 +00:00
run_beaker_tests.sh Support multiple nodetype library beaker tests 2018-07-26 13:18:09 +02:00
run_lint_tests.sh Add CI scripts 2016-07-26 13:28:09 -04:00
run_syntax_tests.sh Remove FUTURE_PARSER 2019-10-10 11:33:04 +02: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://opendev.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.