Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/eirc/puppet-module_skeleton
https://github.com/eirc/puppet-module_skeleton
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/eirc/puppet-module_skeleton
- Owner: eirc
- Created: 2014-11-06T17:36:08.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2014-11-06T20:38:46.000Z (about 10 years ago)
- Last Synced: 2023-03-12T08:37:21.405Z (almost 2 years ago)
- Language: Ruby
- Size: 176 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Module Skeleton
Share common files between different puppet modules.
There are multiple ways to achive this ([modulesync](https://github.com/puppetlabs/modulesync), [puppet-module-skeleton](https://github.com/garethr/puppet-module-skeleton)) but the way I wanted to go is the pure git way.
So over here (more specifically at the [skeleton](https://github.com/eirc/puppet-module_skeleton/tree/skeleton) branch) the module skeleton is kept. To use it in a module your add this repo as a remote and only reference the skeleton branch. The second part is only optional so you don't actually track the master branch which keeps this documentation and is totally useless in that respect.
```bash
git remote add -t skeleton skeleton [email protected]:eirc/puppet-module_skeleton.git
```
Then at any time fetch and merge will bring any new skeleton file updates to the current working branch.
```bash
git fetch skeleton
git merge skeleton/skeleton
```
Obviously any changes that conflict will produce a git conflict and that will just have to be resolved as any other git conflict.
The baseline of the skeleton is produced with `puppet module generate module_skeleton` so a search for `module_skeleton` will reveal places that definitly require manual intervention and the actual module name will have to replace it.