Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/rattermeyer/puppet-ci-profiles
https://github.com/rattermeyer/puppet-ci-profiles
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/rattermeyer/puppet-ci-profiles
- Owner: rattermeyer
- Created: 2014-07-08T21:58:05.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2014-08-24T09:01:31.000Z (over 10 years ago)
- Last Synced: 2024-10-14T08:07:27.732Z (2 months ago)
- Language: Puppet
- Size: 141 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Profiles
First thought about inheritance. But node inheritance is not recommended.
Then thought of composition. I wanted to compose a node definition from parts or profiles.
So I came up with this profile module.# Open issues / Still bothers me
According to my current understanding, I need to have all modules available, that are referenced
from any of the classes contained in this module. This would mean, I need to either rethink my requirement _one module for all profiles, I currently need_ or
need to find a different way to do it in Puppet