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.
Description of problem:
<jweiss-pto> i would have expected: R, RU, CRU, CRUD. It appears there is R,
RD, RU, CRUD [17:50]
<jweiss-pto> i would have thought CRU is way more useful than RD [17:51]
<jweiss-pto> who would ever get the "delete" role?
I have a hard time thinking of a use case for the delete role - some kind of grim reaper user who only deletes things?
If there's some use case for Delete, that is fine, but still think we should add "CRU" - Create Read Update (or Modify, as we call it in the UI). Otherwise there is no way to give a user permission to create, without giving him full admin permission.
Version-Release number of selected component (if applicable):
katello-0.1.175-1.git.19.7ffe744.el6.noarch
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM. If this is a mistake feel free to re-open.
Description of problem: <jweiss-pto> i would have expected: R, RU, CRU, CRUD. It appears there is R, RD, RU, CRUD [17:50] <jweiss-pto> i would have thought CRU is way more useful than RD [17:51] <jweiss-pto> who would ever get the "delete" role? I have a hard time thinking of a use case for the delete role - some kind of grim reaper user who only deletes things? If there's some use case for Delete, that is fine, but still think we should add "CRU" - Create Read Update (or Modify, as we call it in the UI). Otherwise there is no way to give a user permission to create, without giving him full admin permission. Version-Release number of selected component (if applicable): katello-0.1.175-1.git.19.7ffe744.el6.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: