From 5d2cd5cd193e2d11250fdcd216d0d8e03ba642ee Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Thu, 14 Feb 2019 20:22:09 -0800 Subject: [PATCH] Add known issue to release notes, and update tag pruning page --- ee/dtr/release-notes.md | 1 + ee/dtr/user/tag-pruning.md | 10 ++++++++-- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/ee/dtr/release-notes.md b/ee/dtr/release-notes.md index 497cf07e83..5c8b86ced6 100644 --- a/ee/dtr/release-notes.md +++ b/ee/dtr/release-notes.md @@ -84,6 +84,7 @@ to upgrade your installation to the latest release. * Users with read-only permissions to a repository can edit the repository README but their changes will not be saved. Only repository admins should have the ability to [edit the description](/ee/dtr/admin/manage-users/permission-levels/#team-permission-levels) of a repository. (docker/dhe-deploy #9677) * Poll mirroring for Docker plugins such as `docker/imagefs` is currently broken. (docker/dhe-deploy #9490) * When viewing the details of a scanned image tag, the header may display a different vulnerability count from the layer details. (docker/dhe-deploy #9474) + * In order to set a tag limit for pruning purposes, immutability must be turned off for a repository. This limitation is not clear in the **Repository Settings** view. (docker/dhe-deploy #9554) * Webhooks * When configured for "Image promoted from repository" events, a webhook notification is triggered twice during an image promotion when scanning is enabled on a repository. (docker/dhe-deploy #9685) diff --git a/ee/dtr/user/tag-pruning.md b/ee/dtr/user/tag-pruning.md index a12fbccac6..6853a0c777 100644 --- a/ee/dtr/user/tag-pruning.md +++ b/ee/dtr/user/tag-pruning.md @@ -11,11 +11,14 @@ Tag pruning is the process of cleaning up unnecessary or unwanted repository tag * specifying a tag pruning policy or alternatively, * setting a tag limit - > Tag Pruning > > When run, tag pruning only deletes a tag and does not carry out any actual blob deletion. For actual blob deletions, see [Garbage Collection](../../admin/configure/garbage-collection.md). +> Known Issue +> +> While the tag limit field is disabled when you turn on immutability for a new repository, this is currently [not the case with **Repository Settings**](/ee/dtr/release-notes/#known-issues). As a workaround, turn off immutability when setting a tag limit via **Repository Settings > Pruning**. + In the following section, we will cover how to specify a tag pruning policy and set a tag limit on repositories that you manage. It will not include modifying or deleting a tag pruning policy. ## Specify a tag pruning policy @@ -65,7 +68,10 @@ In addition to pruning policies, you can also set tag limits on repositories tha ![](../images/tag-pruning-4.png){: .with-border} -To set a tag limit, select the repository that you want to update and click the **Settings** tab. Specify a number in the **Pruning** section and click **Save**. The **Pruning** tab will now display your tag limit above the prune triggers list along with a link to modify this setting. +To set a tag limit, do the following: +1. Select the repository that you want to update and click the **Settings** tab. +2. Turn off immutability for the repository. +3. Specify a number in the **Pruning** section and click **Save**. The **Pruning** tab will now display your tag limit above the prune triggers list along with a link to modify this setting. ![](../images/tag-pruning-5.png){: .with-border}