Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
1. Proposed title of this feature request
Add option to lock template at the time of import using foreman_templates plugin.
3. What is the nature and description of the request?
Add an option to the import using foreman_templates that will import the template and lock it.
4. Why does the customer need this? (List the business requirements here)
As a measure of preventing edits to the templates from the Satellite itself when the development workflow of the templates is in git.
5. How would the customer like to achieve this? (List the functional requirements here)
Perhaps add a flag so that when a template is imported, it will immediately lock the template.
6. For each functional requirement listed in question 5, specify how Red Hat
and the customer can test to confirm the requirement is successfully implemented.
Using the locking flag, the template would then appear locked within the templates section of the webUI
7. Is there already an existing RFE upstream or in Red Hat bugzilla?
I do not believe so.
8. Does the customer have any specific timeline dependencies?
No
9. Is the sales team involved in this request and do they have any additional input?
No
10. List any affected packages or components.
tfm-rubygem-foreman_templates
11. Would the customer be able to assist in testing this functionality if implemented?
Absolutely.
Verified on Satellite 6.5 snap 2 with
foreman-rake templates:import repo=https://github.com/theforeman/community-templates branch=develop prefix='[community] ' lock=true
Imported templates are locked as expected
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:1222