Feature #11182
closed
As a user i like to attach a site.pp to a content view that includes Puppet modules
Description
Use case:
We use a site.pp to define Puppet stages and a bucket configuration.
If we use the Puppet module management from Katello/Satellite 6, we are forced to create one central site.pp.
Some of our organisations might not like that central configuration and we would be have to write some logic
around it.
What i like to see as a new feature is the ability to attach a site.pp to a content view that contains Puppet modules.
The uploaded or edited site.pp should then get moved to the environments ./manifests/site.pp file and synchronised
over all capsules.
Updated by Eric Helms over 8 years ago
- Status changed from New to Need more information
- Triaged changed from No to Yes
A few questions:
- You could achieve this by creating a puppet module that contained only that particular manifest at present?
- Sounds like the more generic feature being requested is the ability to create/manage individual puppet manifests outside of a module?
Updated by Anonymous over 8 years ago
Eric Helms wrote:
A few questions:
- You could achieve this by creating a puppet module that contained only that particular manifest at present?
- Sounds like the more generic feature being requested is the ability to create/manage individual puppet manifests outside of a module?
We use the site.pp to define run stages and configure Filebucket to backup changed files to the Foreman server.
The site.pp is always run first if there is a manifests directory or if there is an environment.conf file in the environment directory.
If it would be in a module there would be no way to tell this module to run first.
Updated by
Updated by Eric Helms over 8 years ago
- translation missing: en.field_release set to 114
Updated by John Mitsch over 4 years ago
- Status changed from Need more information to Rejected
- Target version deleted (
Katello Backlog)
Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.