Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-2305

user with object permissions (not global) on the repo can't add/remove cv

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2.4, crc-2023-06-27
    • 2.4
    • UI
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Release Note Not Required

      Steps to reproduce

      1-Login with admin

      2-create a new user (user_1)

      3-create a new group (group_1)

      4-add user_1 to group_1

      5-create a repo (repo_1)

      6-Go to repo_1 --> access --> select group_1 and add permissions

      7-Login with user_1

      8-Go to repo_1

       

      Expected result

      User is owner of the repo. User can put collections there and remove them.

       

      Actual result

      User can't add/remove CV.

            [AAH-2305] user with object permissions (not global) on the repo can't add/remove cv

            the permission check on the Edit form was running before we had a chance to load the item to check for object permissions .. fixing in https://github.com/ansible/ansible-hub-ui/pull/3628

            Martin Hradil added a comment - the permission check on the Edit form was running before we had a chance to load the item to check for object permissions .. fixing in https://github.com/ansible/ansible-hub-ui/pull/3628

            I'm reopening this one because a user having this role galaxy.ansible_repository_owner (object permission) can't Edit the repo. If the role is assigned to the group (global), the user can.

            Christian Torrens (Inactive) added a comment - I'm reopening this one because a user having this role galaxy.ansible_repository_owner (object permission) can't Edit the repo. If the role is assigned to the group (global), the user can.

            CPaaS Service Account mentioned this issue in a merge request of aap-cpaas / config / python-galaxy-ng on branch ansible-automation-platform-2.4_upstream_6f4028f98150ad7442ebff5977ed390c:

            Updated US source to: 3b00f73 Fix EmptyStateFilter not appearing in Namespace detail when filtering by repo/tags/sign state (#3597) (#3604)

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of aap-cpaas / config / python-galaxy-ng on branch ansible-automation-platform-2.4_ upstream _6f4028f98150ad7442ebff5977ed390c : Updated US source to: 3b00f73 Fix EmptyStateFilter not appearing in Namespace detail when filtering by repo/tags/sign state (#3597) (#3604)

            CPaaS Service Account mentioned this issue in a merge request of aap-cpaas / config / automation-hub on branch ansible-automation-platform-2.4_upstream_10739f4e49116f14c3edbef33ff3089a:

            Updated US source to: 3b00f73 Fix EmptyStateFilter not appearing in Namespace detail when filtering by repo/tags/sign state (#3597) (#3604)

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of aap-cpaas / config / automation-hub on branch ansible-automation-platform-2.4_ upstream _10739f4e49116f14c3edbef33ff3089a : Updated US source to: 3b00f73 Fix EmptyStateFilter not appearing in Namespace detail when filtering by repo/tags/sign state (#3597) (#3604)

            indeed, the collection versions tab was ignoring any object permissions
            fixing in https://github.com/ansible/ansible-hub-ui/pull/3602

            Martin Hradil added a comment - indeed, the collection versions tab was ignoring any object permissions fixing in https://github.com/ansible/ansible-hub-ui/pull/3602

              mhradil-1 Martin Hradil
              ctorrens@redhat.com Christian Torrens (Inactive)
              Christian Torrens Christian Torrens (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: