Skip to content
BranchesTags

Latest commit

 

History

118 Commits

Folders and files

NameName
Last commit message
Last commit date
README.md
README.md
 
 

Repository files navigation

quay-api

To use the api you have to have a bearer token in place with the correct scope

export bearer_token=XXXXXXXXXXXXXXXX
export quay_registry=REGISTRY_FQDN_OR_IP
export orga=ORGANIZATION_NAME
export email=email@domain.tld
export repo=REPOSITORY_NAME
export policy_uuid=POLICY_UUID
export tag=TAG
export newtag=NEWTAG
export manifest_digest=MANIFEST_DIGEST
export team=TEAM_NAME
export user=USER_NAME
export robot=ROBOT_SHORT_NAME
export quota_id=QUOTA_ID

Tested with quay version 3.11.0

Table of contents

Organizations (Namespaces)

List all existing organizations

Token scope: super:user

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/superuser/organizations/ | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/superuser/organizations/ | jq

Create the organization $orga

Setting email is optional!

The email has to be unique registry-wide!

If not set a random uuid in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx will be stored

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "name": "${orga}", \
              "email": "${email}" \
             }' \
     https://${quay_registry}/api/v1/organization/ | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"name": "${orga}"}, "email": "${email}"}' https://${quay_registry}/api/v1/organization/ | jq

Success is HTTP 201

Set or modify email info for existing organization orga

The email has to be unique registry-wide!

To delete an existing email overwrite it with a random uuid in the format xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

python -m uuid will do the trick!

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "email": "'${email}'" \
             }' \
     https://${quay_registry}/api/v1/organization/${orga} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"email": "'${email}'"}' https://${quay_registry}/api/v1/organization/${orga} | jq

Success is HTTP 200, no success is HTTP 400

Get the details for the organization $orga

Token scope: super:user or org:admin or repo:create

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga} | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga} | jq

Success is HTTP 200, no success is HTTP 404

List the applications for the organization $orga

Token scope: org:admin

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/applications | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/applications | jq

Success is HTTP 200

Delete the organization $orga

Token scope: super:user or org:admin

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga} | jq

Success is HTTP 204, no success is HTTP 403

Prototypes (Default permissions)

Default permissions are granted automatically to newly created repositories, in addition to the default of the repository's creator. Default permissions are not added to already existing repositories.

Get current existing permission protoypes

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

Success is HTTP200

Create a permission prototype for team $team to admin

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "delegate": {\
                           "name": "${team}", \
                           "kind": "team" \
                           }, \
              "role": "admin"              
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"delegate":{"name": "${team}","kind": "team"}, "role": "admin"}' https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

Required properties are delegate and role

Optional properties is activating_user

Property delegate requires name and kind Property activating_user requires name

  • Valid values for role are admin, write and read
  • Valid values for kind are team and user

Success is HTTP200

Create a permission prototype for user $user to write

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "delegate": {\
                           "name": "${user}", \
                           "kind": "user" \
                           }, \
              "role": "write"              
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"delegate":{"name": "${user}","kind": "user"}, "role": "write"}' https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

Required properties are delegate and role

Optional properties is activating_user

Property delegate requires name and kind Property activating_user requires name

  • Valid values for role are admin, writeandread`
  • Valid values for kind are team and user

Success is HTTP200

Create a permission prototype for robot $robot to read

A robot is a user with the robot acount name (${orga}+${robot})

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "delegate": {\
                           "name": "'${orga}+${robot}'", \
                           "kind": "user" \
                           }, \
              "role": "read"              
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"delegate":{"name": "'${orga}+${robot}'","kind": "user"}, "role": "read"}' https://${quay_registry}/api/v1/organization/${orga}/prototypes | jq

Required properties are delegate and role

Optional properties is activating_user

Property delegate requires name and kind Property activating_user requires name

  • Valid values for role are admin, writeandread`
  • Valid values for kind are team and user

Success is HTTP200

Delete a prototype permission

Get ${prototypes_id} by querying the prototypes

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/prototypes/${prototypes_id} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token} https://${quay_registry}/api/v1/organization/${orga}/prototypes/${prototypes_id} | jq

Success is HTTP204

Auto-prune policy registry-wide

Auto-pruning policy registry-wide is available since quay v3.12.0

The registry-wide auto-prune policy works to all organizations and repository as a default policy.

There can only be one policy at a time.

The registry-wide auto-prune policy is defined in the config.yaml with the config field DEFAULT_NAMESPACE_AUTOPRUNE_POLICY and can only be changed there.

A change requires a restart of Quay!

List the current registry-wide auto-prune policy

curl https://${quay_registry}/config | jq '.config.DEFAULT_NAMESPACE_AUTOPRUNE_POLICY'

Auto-prune policy for organizations (Namespaces)

Auto-pruning policies for organizations are available since quay v3.10.0

Auto-pruning policies work at the organization level and apply to all repositories of this organization.

There can only be one policy at a time.

List the current auto-prune policy for organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/ | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/ | jq

Success is HTTP 200

If there is no auto-prune policy set the response will be an empty array policies. E.g.{"policies": []}

If there is an existing auto-prune policy the response is the array policies containing the current set policy. E.g. {"policies": [{"uuid": "cb44b3b7-bca6-42e4-8eaf-4350f09b5a63", "method": "number_of_tags", "value": 10}]}

Get the uuid of the existing auto-prune policy for organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/ | jq -r '.policies[].uuid'

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/ | jq -r '.policies[].uuid'

Success is HTTP 200

Set the auto-prune policy for organization $orga

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{ \
              "method": "creation_date", \
              "value": "30d" \
             }' \
     https://${quay_registry}/api/v1/organization/ ${orga}/autoprunepolicy/ | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"method": "creation_date", "value": "30d"}' https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/ | jq

Success is HTTP 201, no success is HTTP 400

Valid method values are

  • creation_date
  • number_of_tags.

Method number_of_tags expects an integer.

Method creation_date expects a string containing the amount of time the image is not deleted since creation. Valid options are

  • s seconds
  • m minutes
  • h hours
  • d days
  • w weeks

E.g. 30d.

Modify the existing auto-prune policy for organization $orga

First, get the current uuid (${policy_uuid}) to modify it

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{ \
              "method": "creation_date", \
              "value": "7d" \
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/${policy_uuid} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"method": "creation_date"}, "value": "7d"' https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/${policy_uuid} | jq

Success is HTTP 204, no success is HTTP 404

Successful modification has no response!

Delete the existing auto-prune policy for organization $orga

First, get the current uuid (${policy_uuid}) to delete it

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/${policy_uuid} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/${policy_uuid} | jq

Success is HTTP 200, no success is HTTP 404

A successful deletion will return the deleted uuid. E.g. {"uuid": "cb44b3b7-bca6-42e4-8eaf-4350f09b5a63"}

Auto-prune policy for User (Current user)

Auto-pruning policies for the current user are available since quay v3.10.0

The current user is the user who created the bearer token in use.

There can only be one policy at a time.

List the current auto-prune policy for the current user

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/user/autoprunepolicy/ | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/user/autoprunepolicy/ | jq

Success is HTTP 200

If there is no auto-prune policy set the response will be an empty array policies. E.g.{"policies": []}

If there is an existing auto-prune policy the response is the array policies containing the current set policy. E.g. {"policies": [{"uuid": "cb44b3b7-bca6-42e4-8eaf-4350f09b5a63", "method": "number_of_tags", "value": 10}]}

Get the uuid of the existing auto-prune policy for the current user

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/user/autoprunepolicy/ | jq -r '.policies[].uuid'

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/user/autoprunepolicy/ | jq -r '.policies[].uuid'

Success is HTTP 200

Set the auto-prune policy for the current user

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{ \
              "method": "creation_date", \
              "value": "30d" \
             }' \
     https://${quay_registry}/api/v1/user/autoprunepolicy/ | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"method": "creation_date", "value": "30d"}' https://${quay_registry}/api/v1/user/autoprunepolicy/ | jq

Success is HTTP 201, no success is HTTP 400

Valid method values are

  • creation_date
  • number_of_tags.

Method number_of_tags expects an integer.

Method creation_date expects a string containing the amount of time the image is not deleted since creation. Valid options are

  • s seconds
  • m minutes
  • h hours
  • d days
  • w weeks

E.g. 30d.

Modify the existing auto-prune policy for the current user

First, get the current uuid (${policy_uuid}) to modify it

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{ \
              "method": "creation_date", \
              "value": "7d" \
             }' \
     https://${quay_registry}/api/v1/user/autoprunepolicy/${policy_uuid} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"method": "creation_date", "value": "7d"}' https://${quay_registry}/api/v1/user/autoprunepolicy/${policy_uuid} | jq

Success is HTTP 204, no success is HTTP 404

Successful modification has no response!

Delete the existing auto-prune policy for the current user

First, get the current uuid (${policy_uuid}) to delete it

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/user/autoprunepolicy/${policy_uuid} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/user/autoprunepolicy/${policy_uuid} | jq

Success is HTTP 200, no success is HTTP 404

A successful deletion will return the deleted uuid. E.g. {"uuid": "cb44b3b7-bca6-42e4-8eaf-4350f09b5a63"}

Auto-prune policy for Repositories

Auto-pruning policies for repositories are available since quay v3.11.0

Auto-pruning policies on the repository level work for organizations and users in the same way. Use for user repositories the user name as ${orga}!

There can only be one policy at a time.

List the current auto-prune policy for repository $repo within the organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/ | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/ | jq

Success is HTTP 200

If there is no auto-prune policy set the response will be an empty array policies. E.g.{"policies": []}

If there is an existing auto-prune policy the response is the array policies containing the current set policy. E.g. {"policies": [{"uuid": "cb44b3b7-bca6-42e4-8eaf-4350f09b5a63", "method": "number_of_tags", "value": 10}]}

Get the uuid of the existing auto-prune policy for repository $repo within the organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/ | jq -r '.policies[].uuid'

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/ | jq -r '.policies[].uuid'

Success is HTTP 200

Set the auto-prune policy for repository $repo within the organization $orga

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{ \
              "method": "creation_date", \
              "value": "30d" \
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/ | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"method": "creation_date", "value": "30d"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/ | jq

Success is HTTP 201, no success is HTTP 400

The response is the uuid for the created policy. E.g. {"uuid": "cb44b3b7-bca6-42e4-8eaf-4350f09b5a63"}

Valid method values are

  • creation_date
  • number_of_tags.

Method number_of_tags expects an integer.

Method creation_date expects a string containing the amount of time the image is not deleted since creation. Valid options are

  • s seconds
  • m minutes
  • h hours
  • d days
  • w weeks

E.g. 30d.

Modify the existing auto-prune policy for repository $repo within the organization $orga

First, get the current uuid (${policy_uuid}) to modify it

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{ \
              "method": "creation_date", \
              "value": "7d" \
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/${policy_uuid} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"method": "creation_date", "value": "7d"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/autoprunepolicy/${policy_uuid} | jq

Success is HTTP 204, no success is HTTP 404

Successful modification has no response!

Delete the existing auto-prune policy for repository $repo within the organization $orga

First, get the current uuid (${policy_uuid}) to delete it

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/${policy_uuid} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/autoprunepolicy/${policy_uuid} | jq

Success is HTTP 200, no success is HTTP 404

A successful deletion will return the deleted uuid. E.g. {"uuid": "cb44b3b7-bca6-42e4-8eaf-4350f09b5a63"}

Repositories

List all repositories the user who created the token has access to

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository?public=true | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository?public=true | jq

List all existing repositories in organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository?namespace=${orga} | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository?namespace=${orga} | jq

Create the repository $repo in organization $orga

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "namespace": "'$orga'", \
              "repository": "'$repo'", \
              "visibility": "public", \
              "description": "", \
              "repo_kind": "image" \
             }' \
     https://${quay_registry}/api/v1/repository | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"namespace": "'$orga'","repository": "'$repo'","visibility": "public","description": "","repo_kind": "image"}' https://${quay_registry}/api/v1/repository | jq

Success is HTTP 201, no success is HTTP 400

Required properties are namespace, repository, visibility and description

Optional property is repo_kind which defaults to image

  • Valid values for visibility are public or private
  • Valid values for description are empty string or markdown encoded text
  • Valid values for repo_kind are image or application

Change the visibility of the repository $repo within the organization $orga to public

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "visibility": "public"\
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/changevisibility | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"visibility": "public"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/changevisibility | jq

Success is HTTP 200, no success is HTTP 400

Valid values are public or private

Change the repository state to Readonly for repository $repo within the organization $orga

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "state": "READ_ONLY"\
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/changestate | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"state": "READ_ONLY"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/changestate | jq

Success is HTTP 200

Valid values are NORMAL, READ_ONLY and MIRROR... take care it's case sensitive!

Delete the repository $repo within the organization $orga

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" https://${quay_registry}/api/v1/repository/${orga}/${repo} | jq

Success is HTTP 204 (even if $repo does not exist!), no success is HTTP 500 (only if $orga does not exist!)

Mirrored repositories (needs to be reviewed!)

Get the existing mirror config from the repository $repo within the organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

Success is HTTP 200, no success is HTTP 404 if there's no mirror config

Create a mirror config for the mirrored repository $repo within the organization $orga (quay.io/minio/mc:latest)

The used robot orga+robot must already exist!

Required values to provide are

  • external_reference
  • sync_interval
  • sync_start_date
  • root_rule
    • rule_kind is always tag_glob_csv
    • rule_value is a list of tags to sync... * is only valid if there's the tag latest at the source. If this is not the case define an existing tag and *

Optional values are

  • is_enabled if set to true the repository state will be switched to MIRROR
  • external_registry_username
  • external_registry_password
  • external_registry_config
    • unsigned_images
    • verify_tls
    • proxy
      • http_proxy
      • https_proxy
      • no_proxy
  • sync_expiration_date

Minimal config:

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "external_reference": "quay.io/minio/mc", \
              "external_registry_username": "", \
              "sync_interval": 600, \
              "sync_start_date": "2021-08-06T11:11:39Z", \
              "root_rule": {\
                            "rule_kind": "tag_glob_csv", \
                            "rule_value": [ "latest" ]\
                           }, \
              "robot_username": "orga+robot"\
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"external_reference": "quay.io/minio/mc", "external_registry_username": "", "sync_interval": 600, "sync_start_date": "2021-08-06T11:11:39Z", "root_rule": {"rule_kind": "tag_glob_csv", "rule_value": [ "latest" ]}, "robot_username": "orga+robot"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

Extended config

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"is_enabled": true, "external_reference": "quay.io/minio/mc", "external_registry_username": "username", "external_registry_password": "password", "external_registry_config": {"unsigned_images":true, "verify_tls": false, "proxy": {"http_proxy": "http://proxy.tld", "https_proxy": "https://proxy.tld", "no_proxy": "domain"}}, "sync_interval": 600, "sync_start_date": "2021-08-06T11:11:39Z", "root_rule": {"rule_kind": "tag_glob_csv", "rule_value": [ "*" ]}, "robot_username": "orga+robot"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "is_enabled": true, \
              "external_reference": "quay.io/minio/mc", \
              "external_registry_username": "username", \
              "external_registry_password": "password", \
              "external_registry_config": {\
                                           "unsigned_images":true, \
                                           "verify_tls": false, \
                                           "proxy": {\
                                                     "http_proxy": "http://proxy.tld", \
                                                     "https_proxy": "https://proxy.tld", \
                                                     "no_proxy": "domain"\
                                                     }\
                                          }, \
                                          "sync_interval": 600, \
                                          "sync_start_date": "2021-08-06T11:11:39Z", \
                                          "root_rule": {\
                                                        "rule_kind": "tag_glob_csv", \
                                                        "rule_value": [ "*" ]\
                                                       }, \
                                          "robot_username": "orga+robot"\
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

Success is HTTP 201, no success is HTTP 409 if a mirror config already exists

Update a part of the mirror config of the mirrored repository $repo within the organization $orga (quay.io/minio/mc:latest)

Here only the sync interval will be updated

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "sync_interval": 1260\
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"sync_interval": 1260}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror | jq

Success is HTTP 201, no sucess is HTTP 404 if there is no mirror config

Initiate a mirror sync action of the mirrored repository $repo within the organization $orga

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror/sync-now | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror/sync-now | jq

Success is HTTP 204

Cancel a mirror sync action of the mirrored repository $repo within the organization $orga

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror/sync-cancel | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/mirror/sync-cancel | jq

Success is HTTP 204

Tags

List all tags in repository $repo within organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/ | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/ | jq

Success is HTTP 200, repo does not exist is HTTP 404

List all active tags in repository $repo within organization $orga

Active tags are the currently available (active) tags, not deleted tags still restoreable from the time machine

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/?onlyActiveTags=true | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/?onlyActiveTags=true | jq

Success is HTTP 200, repo does not exist is HTTP 404

Create a new tag $newtag for manifest digest $manifest_digest in reopsitory $repo within organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "manifest_digest": "sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
             }' \  
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${newtag} | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"manifest_digest": "sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${newtag} | jq

The provided manifest digest has to be the full digest in format sha256:64-characters

Success is HTTP201

Set or change the expiration date to Tue May 2 16:33:45 CEST 2023 of tag $tag for repository $repo in organization $orga

Convert given date into a UNIX time stamp

date -d "2023-05-02 16:33:45 CEST" +%s
1683038025

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "expiration": 1683038025 \
             }' \  
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${tag} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"expiration": 1683038025}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${tag} | jq

Success is HTTP 201

Reset the expiration date to Never (delete the expiration date) of tag $tag in reopsitory $repo within organization $orga

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "expiration": null \
             }' \  
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${tag} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"expiration": null}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${tag} | jq

Success is HTTP 201

Delete tag $tag in repository $repo within organization $orga

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${tag} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/tag/${tag} | jq

Success is HTTP 204

Teams

List all teams within organization $orga (and additional info)

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga} | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga} | jq

Create a team $team within the organization $orga with role member

Required value to provide is

  • role valid values are member, creator or admin
curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "role": "member", \
              "description": "Short description of the team"\
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"role": "member", "description": "Short description of the team"}' https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

success is HTTP 200

Change the role to admin of the team $team within the organization $orga

valid values for role are member, creator or admin

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "role": "admin"\
             }' \
     https://${quay_registry}/api/v1/repository/orga/repo/permissions/team/orgateam | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/orga/repo/permissions/team/orgateam -H "Content-Type: application/json" --data '{"role": "admin"}' | jq

Success is HTTP200

Set or change the description of the team $team within the organization $orga using standard text

Required value to provide is

  • role valid values are member, creator or admin
  • description
curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "role": "member", \
              "description": "Short description of the team"\
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"role": "member", "description": "Short description of the team"}' https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

success is HTTP 200

Set or change the description of the team $team within the organization $orga using markdown text

Required value to provide is

  • role valid values are member, creator or admin
  • description
curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "role": "member", \
              "description": "# Caption\nShort description of the *team*"\
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"role": "member", "description": "# Caption\nShort description of the *team*"}' https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

success is HTTP 200

Add the user $user as member to the team $team in the organization $orga

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team}/members/${user} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/team/${team}/members/${user} | jq

Success is HTTP 200

Get all members of the team $team in organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team}/members | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/team/${team}/members | jq

Remove the user $user as member of the team $team within the organization $orga

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team}/members/${user} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/team/${team}/members/${user} | jq

Success is HTTP 204

Get all permissions for team $team in organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team}/permissions | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/team/${team}/permissions | jq

Success is HTTP 200

Delete the team $team within the organization $orga

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/team/${team} | jq

success is HTTP 204

Enable LDAP group team sync

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "group_dn": "cn=ldapgroup,dc=domain,dc=tld" \
             }' \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team}/syncing | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"group_dn": "cn=ldapgroup,dc=domain,dc=tld"}' https://${quay_registry}/api/v1/organization/${orga}/team/${team}/syncing | jq

success is HTTP 200, could not sync to group: group does not exist or is empty is HTTP 400

Remove LDAP group team sync

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/team/${team}/syncing | jq


curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/team/${team}/syncing | jq

success is HTTP 200

Current User

The current user is the user who created the used bearer_token

Get info about the current user

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/user/ | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/user/ | jq

Success is HTTP 200

Verify the password of the current user

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "password": "'${password}'"
             }' \
     https://${quay_registry}/api/v1/signin/verify | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"password": "'${password}'"}' https://${quay_registry}/api/v1/signin/verify | jq

Success is HTTP 200, invalid credential is HTTP 403

Users

Get all existing users

Existing users are users created if quay is configured with AUTHENTICATION_TYPE: database or has logged in successfully at least once if quay is configured with AUTHENTICATION_TYPE: LDAP

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/superuser/users/ | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/superuser/users/ | jq

Success is HTTP 200

Create an user ${user} with email ${email}

Works only if quay is configured with AUTHENTICATION_TYPE: database

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "username": "'${user}'", \
              "email": "'${email}'"\
             }' \
     https://${quay_registry}/api/v1/superuser/users/ | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"username": "'${user}'", "email": "'${email}'"}' https://${quay_registry}/api/v1/superuser/users/ | jq

Success is HTTP 200, user already exists or email is already in use is HTTP 400

Get user information of user $user

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/users/${user} | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/users/${user} | jq

Success is HTTP 200, no success is HTTP 404

Delete the user $user and all repositories owned by the user

Superusers can't be deleted!

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/superuser/users/$user | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/superuser/users/$user | jq

Success is HTTP 200, no success is HTTP 404

OrgRobots

Create the orgrobot $robot within the organization $orga

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/robots/${robot} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/robots/${robot} | jq

Success is HTTP 201, no success is HTTP 400

Get information about orgrobot $robot (including the robot token) within the organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/robots/${robot} | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/robots/${robot} | jq

Success is HTTP 200, no success is HTTP 400

List all existing orgrobots within the organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/robots | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/robots | jq

Success is HTTP 200

All robots and their tokens are listed

Replace the current token of orgrobot $robot with a new token within the organization $orga

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/robots/${robot}/regenerate | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/robots/${robot}/regenerate | jq

Success is HTTP 200

This will delete the old token and all current logins of this robot will become invalid immediately

Get the current permissions of orgrobot $robot within the organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/robots/${robot}/permissions | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/robots/${robot}/permissions | jq

Success is HTTP 200, no success is HTTP 400

Set or replace current permission to admin for orgrobot $robot for repository $repo within the organization $orga

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "role": "admin" \
             }' \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/permissions/user/${orga}+${robot} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"role": "admin"}' https://${quay_registry}/api/v1/repository/${orga}/${repo}/permissions/user/${orga}+${robot} | jq

Success is HTTP 200, no success is HTTP 400

Valid values are read, write or admin

Delete current permission for orgrobot $robot for repository $repo within the organization $orga

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/${orga}/${repo}/permissions/user/${orga}+${robot} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/${orga}/${repo}/permissions/user/${orga}+${robot} | jq

Success is HTTP 204, no success is HTTP 400

Delete the orgrobot $robot within the organization $orga

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/robots/${robot} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/organization/${orga}/robots/${robot} | jq

Success is HTTP 204, no success is HTTP 400

UserRobots (needs to be reviewed!)

List all existing robots of the current user

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/user/robots | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/user/robots | jq

Success is HTTP 200

Set the permission write to orgrobot $robot for repository $repo within organization $orga

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H "Content-Type: application/json" \
     --data '{\
              "role": "write"\
             }' \
     https://${quay_registry}/api/v1/repository/orga/repo/permissions/user/orga+robby | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H "Content-Type: application/json" --data '{"role": "write"}' https://${quay_registry}/api/v1/repository/orga/repo/permissions/user/orga+robby | jq

Success is HTTP 200, no success is HTTP 400

Valid values are read, write and admin

Delete the current permission for the robot robby for repository repo within organization orga

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/repository/orga/repo/permissions/user/orga+robby | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/repository/orga/repo/permissions/user/orga+robby | jq

Success is HTTP 204, no success is HTTP 400

Quotas

List the current quota of organization $orga

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/quota | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' https://${quay_registry}/api/v1/organization/${orga}/quota | jq

Success is HTTP 200, no success is HTTP 404

Get the quota id of the existing organization quota

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/quota | jq -r '.[].id'

curl -X GET -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' https://${quay_registry}/api/v1/organization/${orga}/quota | jq -r '.[].id'

Success is HTTP 200, no success is HTTP 404

Create a quota of 100MiB for organization $orga using limit_bytes

100 MiB = 104857600 bytes

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H 'Content-Type: application/json' \
     --data '{\
             "limit_bytes": 104857600\
            }' \
     https://${quay_registry}/api/v1/organization/${orga}/quota | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' --data '{"limit_bytes": 104857600}' https://${quay_registry}/api/v1/organization/${orga}/quota | jq

Success is HTTP 201, no success is HTTP 400

Create a quota of 100MiB for organization $orga using limit

The name limit is available since Quay 3.12.0

Valid units are

K|M|G|T|P|E|KB|MB|GB|TB|PB|EB (power-of-10) 1 Kilobyte = 1 KB = 10^3 = 1000 Bytes)

and

Ki|Mi|Gi|Ti|Pi|Ei|KiB|MiB|GiB|TiB|PiB|EiB (power-of-2) 1 Kibibyte= 1 KiB = 2^10 = 1024 Bytes)

Caution 100 MB => 95.4 MiB

Only integers are allowed to set, no floats!

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H 'Content-Type: application/json' \
     --data '{\
             "limit": "100 MiB"\
            }' \
     https://${quay_registry}/api/v1/organization/${orga}/quota | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' --data '{"limit": "100 MiB"}' https://${quay_registry}/api/v1/organization/${orga}/quota | jq

Success is HTTP 201, no success is HTTP 400

Modify the existing quota for organization orga to 200MiB using limit_bytes

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H 'Content-Type: application/json' \
     --data '{\
             "limit_bytes": 209715200\
            }' \
     https://${quay_registry}/api/v1/organization/${orga}/quota/${quota_id} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' --data '{"limit_bytes": 209715200}' https://${quay_registry}/api/v1/organization/${orga}/quota/${quota_id} | jq

Success is HTTP 204, no success is HTTP 404

Modify the existing quota for organization orga to 200MiB using limit

The name limit is available since Quay 3.12.0

Valid units are

K|M|G|T|P|E|KB|MB|GB|TB|PB|EB (power-of-10) 1 Kilobyte = 1 KB = 10^3 = 1000 Bytes)

and

Ki|Mi|Gi|Ti|Pi|Ei|KiB|MiB|GiB|TiB|PiB|EiB (power-of-2) 1 Kibibyte= 1 KiB = 2^10 = 1024 Bytes)

Caution 100 MB => 95.4 MiB

Only integers are allowed to set, no floats!

curl -X PUT \
     -H "Authorization: Bearer ${bearer_token}" \
     -H 'Content-Type: application/json' \
     --data '{\
             "limit": "100 MiB"\
            }' \
     https://${quay_registry}/api/v1/organization/${orga}/quota/${quota_id} | jq

curl -X PUT -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' --data '{"limit": "100 MiB"}' https://${quay_registry}/api/v1/organization/${orga}/quota/${quota_id} | jq

Success is HTTP 200, no success is HTTP 400

Delete the existing quota for organization $orga

First, get the current id (${quota_id}) to delete it

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/organization/${orga}/quota/${quota_id} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' https://${quay_registry}/api/v1/organization/${orga}/quota/${quota_id} | jq

Success is HTTP 204, no success is HTTP 404

Take ownership

Take the ownership of organization $orga

Token scope: super:user

curl -X POST \
     -H "Authorization: Bearer ${bearer_token}" \
     -H 'Content-Type: application/json' \
     https://${quay_registry}/api/v1/superuser/takeownership/${orga} | jq

curl -X POST -H "Authorization: Bearer ${bearer_token}" -H 'Content-Type: application/json' https://${quay_registry}/api/v1/superuser/takeownership/${orga} | jq

Success is HTTP 200, no success because orgs does not exist is HTTP 404, no success because of insufficient priviledges is HTTP 403

OAuth 2 access token (Authorizations)

List all existing OAuth 2 access tokens for the current user

Token scope: user:admin

curl -X GET \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/user/authorizations | jq

curl -X GET -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/user/authorizations | jq

Success is HTTP 200

Delete an existing OAuth 2 access token for the current user

Token scope: user:admin

Get ${token_uuid} by querying the authorizations

curl -X DELETE \
     -H "Authorization: Bearer ${bearer_token}" \
     https://${quay_registry}/api/v1/user/authorizations/${token_uuid} | jq

curl -X DELETE -H "Authorization: Bearer ${bearer_token}" https://${quay_registry}/api/v1/user/authorizations/${token_uuid} | jq

Success is HTTP 204

About

No description, website, or topics provided.

Resources

Readme
Activity

Stars

15 stars

Watchers

1 watching

Forks

7 forks
Report repository

Releases

Packages

Contributors