Description

After adding access to a repository to a user group and add galaxy.ansible_repository_owner role , the user can not approve uploaded collections to that repository.

Key Dependency Versions

python39-pulpcore-3.23.2-1.el8ap.noarch

Steps to Reproduce

1) Creaste user test_user with normal user permissions.
2) Create group test_group .
3) Add user test_user to group test_group.
4) Create repository test_repository and grant access to group test_group with added role galaxy.ansible_repository_owner
5) Create namespace "support"
6) Upload a collection to namespace "support"
7) login using user test_user 

Approval tab is not existing and access to /ui/approval-dashboard/ is denied

Actual Behavior

Approval tab is not existing and access to /ui/approval-dashboard/ is denied

Expected Behavior

The user is able to navigate to approval page and approve the collection.

>> when adding the role galaxy.ansible_repository_owner on the group level ,that group owns all repositories which is not the target of the customer and it is needed for the group to own only that repository.

>> The customer is expecting to have the Ability to approve new content for specific private automation hub repository.