Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

I'm currently designing a continuous integration environment for Red Hat builds. We identify a build as consisting of:
1. Kickstart file+snippets
2. Puppet classes

The CI environment always builds test machines against the Library. Releases are managed by creating content views and promoting them to higher (more stable) environments using changesets.

The problem here is that kickstart files and snippets are globally visible. We cannot therefore version them and manage them through the environments, other than by naming conventions - this then requires renaming, and careful changing of associated environment/host-groups when promoting. This is particularly complicated with snippets, which must be renamed, and then the master kickstart edited to ensure it refers to the correct snippets.

It would be extremely useful for provisioning templates to have environment scope and to be promoted via changesets, exactly as we do for puppet modules and packages.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

*** Bug 1268725 has been marked as a duplicate of this bug. ***

Closing this bug out since we do not believe it will be fixed in the next multiple releases due to the priority of this bug as compared to others. If this is a large impact on you, please feel free to re-open it and provide additional information to help us better prioritize it.

Alternatively to the required functionality, you can currently use foreman-templates plugin, that allows synchronization of templates from external git repository.