openstack/puppet-openstack-cookiecutter
Code Issues Proposed changes

fix error url

Browse Source 
Change-Id: Ia6fa4a41ff41d553ea65a3a876e5cdc5cca8f814
This commit is contained in:
huang.zhiping 2018-04-28 18:44:27 +08:00
parent 9db80401f3
commit 2a27185289
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -19,7 +19,7 @@ There are two ways to create the boilerplate for the puppet module.
### Locally
1. Clone locally the [puppet-openstack-cookiecutter](https://git.openstack.org/openstack/cgit/puppet-openstack-cookiecutter) repository.
1. Clone locally the [puppet-openstack-cookiecutter](https://git.openstack.org/cgit/openstack/puppet-openstack-cookiecutter/) repository.
2. Run `cookiecutter /path/to/cloned/repo`
### Remotely (ie. using a git repo)
@ -28,4 +28,4 @@ There are two ways to create the boilerplate for the puppet module.
## What's next
Once the boilerplate created, in order to be compliant with the other modules, the files managed by [msync](https://github.com/puppet-community/modulesync), (or [configs](https://git.openstack.org/openstack/cgit/puppet-modulesync-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.
Once the boilerplate created, in order to be compliant with the other modules, the files managed by [msync](https://github.com/puppet-community/modulesync), (or [configs](https://git.openstack.org/cgit/openstack/puppet-modulesync-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.