Adds tag API commands (#1226)

Co-authored-by: Steven Smith <stevsmit@stevsmit-thinkpadt14gen4.remote.csb>

Author: stevsmit

README.adoc

@@ -217,7 +217,7 @@ You can make content appear only in the upstream by using the `ifdef::upstream`
 ifdef::downstream[]
 == How do I make content appear in downstream but not in upstream?
 
-You can make content appear only in the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/[downstream] by using the `ifdef::downstream` conditional around the content that you only want to appear downstream. For example: 
+You can make content appear only in the link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/[downstream] by using the `ifdef::downstream` conditional around the content that you only want to appear downstream. For example: 
 
 ----
 \ifdef::downstream[]

api/master.adoc

@@ -119,6 +119,8 @@ include::modules/listing-repos-superuser-api.adoc[leveloffset=+3]
 include::modules/managing-organization-quota-superuser-api.adoc[leveloffset=+3]
 include::modules/managing-user-quota-superuser-api.adoc[leveloffset=+3]
 include::modules/retrieving-build-info-superuser-api.adoc[leveloffset=+3]
+//tag
+include::modules/managing-tags-api.adoc[leveloffset=+2]
 
 
 include::modules/managing-service-keys-api.adoc[leveloffset=+3]

deploy_quay/master.adoc

@@ -84,7 +84,7 @@ include::modules/clair-cve.adoc[leveloffset=+3]
 
 .Additional resources
 
-* link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/vulnerability_reporting_with_clair_on_red_hat_quay/index#vulnerability-reporting-clair-quay-overview[Vulnerability reporting with Clair on {productname}]
+* link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/vulnerability_reporting_with_clair_on_red_hat_quay/index#vulnerability-reporting-clair-quay-overview[Vulnerability reporting with Clair on {productname}]
 
 include::modules/proc_deploy_quay_poc_restart.adoc[leveloffset=+2]
 

deploy_quay_on_openshift_op_tng/master.adoc

@@ -54,7 +54,7 @@ include::modules/operator-unmanaged-redis.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-xref:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/configure_red_hat_quay/index#config-fields-redis[Redis configuration fields]
+xref:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/configure_red_hat_quay/index#config-fields-redis[Redis configuration fields]
 
 include::modules/operator-unmanaged-hpa.adoc[leveloffset=+3]
 include::modules/operator-unmanaged-route.adoc[leveloffset=+3]

deploy_red_hat_quay_operator/master.adoc

@@ -51,7 +51,7 @@ include::modules/operator-unmanaged-redis.adoc[leveloffset=+3]
 
 [role="_additional-resources"]
 .Additional resources
-link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/configure_red_hat_quay/index#config-fields-redis[Redis configuration fields]
+link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/configure_red_hat_quay/index#config-fields-redis[Redis configuration fields]
 
 include::modules/operator-unmanaged-hpa.adoc[leveloffset=+3]
 include::modules/operator-unmanaged-route.adoc[leveloffset=+3]
@@ -98,4 +98,4 @@ include::modules/creating-custom-ssl-certs-config-bundle.adoc[leveloffset=+2]
 [role="quay-next-steps"]
 .Next steps
 
-* https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/red_hat_quay_operator_features/[{productname} features]
+* https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_operator_features/[{productname} features]

modules/adding-a-new-tag-to-image-api.adoc

@@ -51,7 +51,7 @@ $ curl -X POST \
 {}
 ----
 
-. To see a list of tags after creating a new tag you can use the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#listrepotags[`GET /api/v1/repository/{repository}/tag/`] command. For example:
+. To see a list of tags after creating a new tag you can use the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#listrepotags[`GET /api/v1/repository/{repository}/tag/`] command. For example:
 +
 [source,terminal]
 ----

modules/adding-managing-labels-api.adoc

@@ -6,12 +6,12 @@
 
 .Prerequisites
 
-* You have link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#creating-oauth-access-token[Created an OAuth access token].
+* You have link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#creating-oauth-access-token[Created an OAuth access token].
 * You have set `BROWSER_API_CALLS_XHR_ONLY: false` in your `config.yaml` file.
 
 .Procedure
 
-. Use the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#getrepomanifest[`GET /api/v1/repository/{repository}/manifest/{manifestref}`] command to retrieve the details of a specific manifest in a repository:
+. Use the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#getrepomanifest[`GET /api/v1/repository/{repository}/manifest/{manifestref}`] command to retrieve the details of a specific manifest in a repository:
 +
 [source,terminal]
 ----
@@ -21,7 +21,7 @@ $ curl -X GET \
   https://<quay-server.example.com>/api/v1/repository/<repository>/manifest/<manifestref>
 ----
 
-. Use the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#listmanifestlabels[`GET /api/v1/repository/{repository}/manifest/{manifestref}/labels`] command to retrieve a list of labels for a specific manifest:
+. Use the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#listmanifestlabels[`GET /api/v1/repository/{repository}/manifest/{manifestref}/labels`] command to retrieve a list of labels for a specific manifest:
 +
 [source,terminal]
 ----
@@ -38,7 +38,7 @@ $ curl -X GET \
 {"labels": [{"id": "e9f717d2-c1dd-4626-802d-733a029d17ad", "key": "org.opencontainers.image.url", "value": "https://github.com/docker-library/busybox", "source_type": "manifest", "media_type": "text/plain"}, {"id": "2d34ec64-4051-43ad-ae06-d5f81003576a", "key": "org.opencontainers.image.version", "value": "1.36.1-glibc", "source_type": "manifest", "media_type": "text/plain"}]}
 ----
 
-. Use the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#getmanifestlabel[`GET /api/v1/repository/{repository}/manifest/{manifestref}/labels/{labelid}`] command to obtain information about a specific manifest:
+. Use the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#getmanifestlabel[`GET /api/v1/repository/{repository}/manifest/{manifestref}/labels/{labelid}`] command to obtain information about a specific manifest:
 +
 [source,terminal]
 ----
@@ -55,7 +55,7 @@ $ curl -X GET \
 {"id": "e9f717d2-c1dd-4626-802d-733a029d17ad", "key": "org.opencontainers.image.url", "value": "https://github.com/docker-library/busybox", "source_type": "manifest", "media_type": "text/plain"}
 ----
 
-. You can add an additional label to a manifest in a given repository with the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#addmanifestlabel[`POST /api/v1/repository/{repository}/manifest/{manifestref}/labels`] command. For example:
+. You can add an additional label to a manifest in a given repository with the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#addmanifestlabel[`POST /api/v1/repository/{repository}/manifest/{manifestref}/labels`] command. For example:
 +
 [source,terminal]
 ----
@@ -77,7 +77,7 @@ $ curl -X POST \
 {"label": {"id": "346593fd-18c8-49db-854f-4cb1fb76ff9c", "key": "example-key", "value": "example-value", "source_type": "api", "media_type": "text/plain"}}
 ----
 
-. You can delete a label using the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#deletemanifestlabel[`DELETE /api/v1/repository/{repository}/manifest/{manifestref}/labels/{labelid}`] command:
+. You can delete a label using the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#deletemanifestlabel[`DELETE /api/v1/repository/{repository}/manifest/{manifestref}/labels/{labelid}`] command:
 +
 [source,terminal]
 ----

modules/adjust-access-user-repo-api.adoc

@@ -13,12 +13,12 @@ Use the following procedure to adjust access settings for a user or robot accoun
 .Prerequisites
 
 * You have created a user account or robot account.
-* You have link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#creating-oauth-access-token[Created an OAuth access token].
+* You have link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#creating-oauth-access-token[Created an OAuth access token].
 * You have set `BROWSER_API_CALLS_XHR_ONLY: false` in your `config.yaml` file.
 
 .Procedure
 
-. Enter the following link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#changeuserpermissions[`PUT /api/v1/repository/{repository}/permissions/user/{username}`] command to change the permissions of a user:
+. Enter the following link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#changeuserpermissions[`PUT /api/v1/repository/{repository}/permissions/user/{username}`] command to change the permissions of a user:
 +
 [source,terminal]
 ----
@@ -36,7 +36,7 @@ $ curl -X PUT \
 {"role": "admin", "name": "quayadmin+test", "is_robot": true, "avatar": {"name": "quayadmin+test", "hash": "ca9afae0a9d3ca322fc8a7a866e8476dd6c98de543decd186ae090e420a88feb", "color": "#8c564b", "kind": "robot"}}
 ----
 
-. To delete the current permission, you can enter the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#deleteuserpermissions[`DELETE /api/v1/repository/{repository}/permissions/user/{username}`] command:
+. To delete the current permission, you can enter the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#deleteuserpermissions[`DELETE /api/v1/repository/{repository}/permissions/user/{username}`] command:
 +
 [source,terminal]
 ----
@@ -46,7 +46,7 @@ $ curl -X DELETE \
   https://<quay-server.example.com>/api/v1/repository/<namespace>/<repository>/permissions/user/<username>
 ----
 +
-This command does not return any output in the CLI. Instead, you can check that the permissions were deleted by entering the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#listrepouserpermissions[`GET /api/v1/repository/{repository}/permissions/user/`] command:
+This command does not return any output in the CLI. Instead, you can check that the permissions were deleted by entering the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#listrepouserpermissions[`GET /api/v1/repository/{repository}/permissions/user/`] command:
 +
 [source,terminal]
 ----

modules/adjusting-repository-access-via-the-api.adoc

@@ -11,7 +11,7 @@ The visibility of your repository can be set to `private` or `public` by using t
 
 .Prerequisites 
 
-* You have link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#creating-oauth-access-token[Created an OAuth access token].
+* You have link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#creating-oauth-access-token[Created an OAuth access token].
 * You have set `BROWSER_API_CALLS_XHR_ONLY: false` in your `config.yaml` file.
 * You have created a repository. 
 

modules/api-tag-deleteFullTag.adoc

@@ -35,3 +35,12 @@ _required_|The name of the tag|string
 |403|Unauthorized access|<<_apierror,ApiError>>
 |404|Not found|<<_apierror,ApiError>>
 |===
+
+[discrete]
+== Example command
+
+[source,terminal]
+----
+$ curl -X DELETE "https://quay-server.example.com/api/v1/repository/<namespace>/<repo_name>/tag/<tag_name>" \
+  -H "Authorization: Bearer <your_access_token>"
+----

modules/automating-quay-using-the-api.adoc

@@ -16,7 +16,7 @@ The following example shows you how you might use a Python script and a cron job
 
 .Procedure
 
-. Create a Python script that executes an API command. The following example is used to delete organization applications using the link:https://docs.redhat.com/en/documentation/red_hat_quay/3/html-single/red_hat_quay_api_guide/index#deleteorganizationapplication[`DELETE /api/v1/organization/{orgname}/applications/{client_id}`] API endpoint.
+. Create a Python script that executes an API command. The following example is used to delete organization applications using the link:https://docs.redhat.com/en/documentation/red_hat_quay/{producty}/html-single/red_hat_quay_api_guide/index#deleteorganizationapplication[`DELETE /api/v1/organization/{orgname}/applications/{client_id}`] API endpoint.
 +
 .example.py file
 [source,python]

modules/clair-troubleshooting-issues.adoc

@@ -9,12 +9,12 @@ Use the following procedures to troubleshoot Clair.
 
 If you are using Clair, ensure that the images you are trying to scan are supported by Clair. Clair has certain requirements and does not support all image formats or configurations.
 
-For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html/manage_red_hat_quay/clair-vulnerability-scanner#clair-vulnerability-scanner-hosts[Clair vulnerability databases]. 
+For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html/manage_red_hat_quay/clair-vulnerability-scanner#clair-vulnerability-scanner-hosts[Clair vulnerability databases]. 
 
 [id="allowlist-clair-updaters"]
 == Allowlisting Clair updaters
 
-If you are using Clair behind a proxy configuration, you must allowlist the updaters in your proxy or firewall configuration. For more information about updater URLs, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html/vulnerability_reporting_with_clair_on_red_hat_quay/clair-concepts#clair-updater-urls[Clair updater URLs].
+If you are using Clair behind a proxy configuration, you must allowlist the updaters in your proxy or firewall configuration. For more information about updater URLs, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html/vulnerability_reporting_with_clair_on_red_hat_quay/clair-concepts#clair-updater-urls[Clair updater URLs].
 
 [id="clair-dependencies-update"]
 == Updating Clair scanner and its dependencies 
@@ -114,7 +114,7 @@ log_level: debug
 [id="checking-clair-configuration"]
 == Checking Clair configuration 
 
-Check your Clair `config.yaml` file to ensure that there are no misconfigurations or inconsistencies that could lead to issues. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/vulnerability_reporting_with_clair_on_red_hat_quay/index#config-fields-overview[Clair configuration overview].
+Check your Clair `config.yaml` file to ensure that there are no misconfigurations or inconsistencies that could lead to issues. For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/vulnerability_reporting_with_clair_on_red_hat_quay/index#config-fields-overview[Clair configuration overview].
 
 [id="inspect-image-metadata"]
 == Inspect image metadata 

modules/clairv4-air-gapped.adoc

@@ -7,4 +7,4 @@
 * On a system with internet access, the vulnerability database updates is performed manually and exported to a disk.
 * The on-disk data is then transferred to the target system with offline media. It is then manually imported.
 
-For more information on air-gapped Clair v4 and using `clairctl`, the command line tool, see https://access.redhat.com/documentation/en-us/red_hat_quay/3/html/deploy_red_hat_quay_on_openshift_with_the_quay_operator/quay_operator_features#clair-disconnected-environments[Manually updating the vulnerability databases for Clair in an air-gapped OpenShift cluster]
+For more information on air-gapped Clair v4 and using `clairctl`, the command line tool, see https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html/deploy_red_hat_quay_on_openshift_with_the_quay_operator/quay_operator_features#clair-disconnected-environments[Manually updating the vulnerability databases for Clair in an air-gapped OpenShift cluster]

modules/con_quay_intro.adoc

@@ -14,7 +14,7 @@
 * Zero downtime garbage collection
 * 24/7 support
 
-Users should check the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/red_hat_quay_release_notes/index#doc-wrapper[{productname} Release Notes] for the latest feature information. 
+Users should check the link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_release_notes/index#doc-wrapper[{productname} Release Notes] for the latest feature information. 
 
 [id="poc-support"]
 = {productname} support
@@ -32,7 +32,7 @@ Users should check the link:https://access.redhat.com/documentation/en-us/red_ha
 
 {productname} includes several core components, both internal and external.
 
-For a fuller architectural breakdown, see the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/red_hat_quay_architecture/index[{productname} architecture] guide.
+For a fuller architectural breakdown, see the link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/red_hat_quay_architecture/index[{productname} architecture] guide.
 
 [id="poc-internal-components"]
 === Internal components

modules/con_schema.adoc

@@ -2,4 +2,4 @@
 [id="quay-schema"]
 = Schema for {productname} configuration
 
-Most {productname} configuration information is stored in the `config.yaml` file. All configuration options are described in the link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/configure_red_hat_quay/index#doc-wrapper[{productname} Configuration Guide].
+Most {productname} configuration information is stored in the `config.yaml` file. All configuration options are described in the link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/configure_red_hat_quay/index#doc-wrapper[{productname} Configuration Guide].

modules/config-disclaimer.adoc

@@ -4,6 +4,6 @@
 
 With both standalone and Operator-based deployments of {productname} certain features and configuration parameters are not actively used or implemented. As a result, feature flags, such as those that enable or disable certain features, and configuration parameters that are not explicitly documented or requested for documentation by Red Hat Support, should only be modified with caution. Unused features or parameters might not be fully tested, supported, or compatible with {productname}. Modifying unused features parameters might lead to unexpected issues or disruptions with your deployment.
 
-For information about configuring {productname} in standalone deployments, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/manage_red_hat_quay/index#advanced-quay-configuration[Advanced {productname} configuration]
+For information about configuring {productname} in standalone deployments, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/manage_red_hat_quay/index#advanced-quay-configuration[Advanced {productname} configuration]
 
-For information about configuring {productname} Operator deployments, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/3/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index#operator-config-cli[Configuring {productname} on {ocp}]
+For information about configuring {productname} Operator deployments, see link:https://access.redhat.com/documentation/en-us/red_hat_quay/{producty}/html-single/deploying_the_red_hat_quay_operator_on_openshift_container_platform/index#operator-config-cli[Configuring {productname} on {ocp}]