Takashi Kajinami abafec8df8 Stop using absolute names for defined resource types
Since Puppet 4, names are always absolute. We already replaced usage of
absolute names for class inclusion, so can do the same for defined
resource types.

Change-Id: I4f3a33bef23ac5b98fa7882cf7f45436d7279230
2025-02-18 14:44:57 +00:00
2019-04-19 19:29:14 +00:00
2018-02-13 00:28:01 +00:00
2025-02-18 20:47:18 +09:00
2015-05-21 21:11:28 +02:00
2020-09-17 01:03:49 +02:00
2016-07-26 13:28:09 -04:00
2020-09-19 00:14:23 +02:00
2019-10-10 11:33:04 +02:00

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.

Description
Cookiecutter template for a compliant OpenStack puppet-modules
Readme 1.7 MiB
Languages
Puppet 39.9%
Ruby 37.5%
Shell 10.8%
Python 10.6%
Pascal 1.2%