第1章 Red Hat Quay permissions model

Procedure

1. On the Red Hat Quay landing page, click the name of your Organization.
2. In the navigation pane, click Teams and Membership.

3. Select the TEAM ROLE drop-down menu, as shown in the following figure:

   

4. For the selected team, choose one of the following roles:

   • Admin. Full administrative access to the organization, including the ability to create teams, add members, and set permissions.
   • Member. Inherits all permissions set for the team.
   • Creator. All member permissions, plus the ability to create new repositories.

Procedure

1. Enter the following GET /api/v1/organization/{orgname}/team/{teamname}/permissions command to return a list of repository permissions for the organization’s team. Note that your team must have been added to a repository for this command to return information.

   $ curl -X GET \
     -H "Authorization: Bearer <your_access_token>" \
     "<quay-server.example.com>/api/v1/organization/<organization_name>/team/<team_name>/permissions"

   Example output

   {"permissions": [{"repository": {"name": "api-repo", "is_public": true}, "role": "admin"}]}

2. You can create or update a team within an organization to have a specified role of admin, member, or creator using the PUT /api/v1/organization/{orgname}/team/{teamname} command. For example:

   $ curl -X PUT \
     -H "Authorization: Bearer <your_access_token>" \
     -H "Content-Type: application/json" \
     -d '{
       "role": "<role>"
     }' \
     "<quay-server.example.com>/api/v1/organization/<organization_name>/team/<team_name>"

   Example output

   {"name": "testteam", "description": "", "can_view": true, "role": "creator", "avatar": {"name": "testteam", "hash": "827f8c5762148d7e85402495b126e0a18b9b168170416ed04b49aae551099dc8", "color": "#ff7f0e", "kind": "team"}, "new_team": false}