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. What is the nature and description of the request?
acl's on channels/repo's for uploading 3rd party rpms from developers
It would also be great that rpm's being uploaded, where checked with gpg signing
2. Why does the customer need this? (List the business requirements here)
we don't want to give access to 3rd party developers to all channels
3. How would the customer like to achieve this? (List the functional requirements here)
access roles for uploading in certain products/repos/contentviews
4. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
admin can upload everywhere, custom user only in channel x
5. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL7, RHEL8)?
rhel7 and above
6. Would the customer be able to assist in testing this functionality if implemented?
Yes
1. What is the nature and description of the request? acl's on channels/repo's for uploading 3rd party rpms from developers It would also be great that rpm's being uploaded, where checked with gpg signing 2. Why does the customer need this? (List the business requirements here) we don't want to give access to 3rd party developers to all channels 3. How would the customer like to achieve this? (List the functional requirements here) access roles for uploading in certain products/repos/contentviews 4. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. admin can upload everywhere, custom user only in channel x 5. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL7, RHEL8)? rhel7 and above 6. Would the customer be able to assist in testing this functionality if implemented? Yes