From 1c944746963f84900fe61770092bdf6003780ffd Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Tue, 16 Oct 2018 20:30:08 -0700 Subject: [PATCH 1/3] Document planned deprecation of current ManifestLists behavior --- ee/dtr/deprecation-notice.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 ee/dtr/deprecation-notice.md diff --git a/ee/dtr/deprecation-notice.md b/ee/dtr/deprecation-notice.md new file mode 100644 index 0000000000..d7ac7f0703 --- /dev/null +++ b/ee/dtr/deprecation-notice.md @@ -0,0 +1,14 @@ +--- +description: Page for deprecation announcements. +keywords: registry, manifest, images, signatures, repository, distribution, digest +title: Deprecation Notice +--- + +This document outlines the functionalities or components within DTR that will be deprecated. + +### Enable Manifest List via the API + +Since `v2.5`, it has been possible for repository admins to enable manifest lists when [creating a repository via the API](./reference/dtr/2.5/api/). You accomplish this by setting `enableManifestLists` to `true` when sending a POST request to the `/api/v0/repositories/{namespace}` endpoint. When enabled for a repository, any image that you push to an existing tag will be added to the list of manifests for that tag. + +The above behavior and the field `enableManifestLists` will be removed in `v2.7`. Starting in `v2.7`, you can use the CLI command, `docker manifest` to [create and push a manifest list to any repository](./edge/engine/reference/commandline/manifest/). + From 62069559fc09088a6572fb44e312d50587835692 Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Thu, 18 Oct 2018 23:27:58 -0700 Subject: [PATCH 2/3] Update deprecation-notice.md Clarify differences in manifest lists behavior between different versions --- ee/dtr/deprecation-notice.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/ee/dtr/deprecation-notice.md b/ee/dtr/deprecation-notice.md index d7ac7f0703..c6c11c0d9d 100644 --- a/ee/dtr/deprecation-notice.md +++ b/ee/dtr/deprecation-notice.md @@ -8,7 +8,15 @@ This document outlines the functionalities or components within DTR that will be ### Enable Manifest List via the API -Since `v2.5`, it has been possible for repository admins to enable manifest lists when [creating a repository via the API](./reference/dtr/2.5/api/). You accomplish this by setting `enableManifestLists` to `true` when sending a POST request to the `/api/v0/repositories/{namespace}` endpoint. When enabled for a repository, any image that you push to an existing tag will be added to the list of manifests for that tag. +#### 2.5 -The above behavior and the field `enableManifestLists` will be removed in `v2.7`. Starting in `v2.7`, you can use the CLI command, `docker manifest` to [create and push a manifest list to any repository](./edge/engine/reference/commandline/manifest/). +Since `v2.5`, it has been possible for repository admins to enable manifest lists when [creating a repository via the API](./reference/dtr/2.5/api/). You accomplish this by setting `enableManifestLists` to `true` when sending a POST request to the `/api/v0/repositories/{namespace}` endpoint. When enabled for a repository, any image that you push to an existing tag will be added to the manifest list for that tag. + +#### 2.6 + +Manifest lists are enabled for tags by default on any repository. There is no need to enable manifest lists using uthe API. + +#### 2.7 + +The `v2.5` behavior and the `enableManifestLists` field will be removed in `v2.7`. Starting in `v2.7`, you can use the CLI command, `docker manifest` to [create and push a manifest list to any repository](./engine/reference/commandline/manifest/). From d50e8141bb524b04c6e3fecb0e1d61235c2c78bf Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Fri, 19 Oct 2018 14:04:20 -0700 Subject: [PATCH 3/3] Update deprecation-notice.md Final edit based on sync-up with @caervs . --- ee/dtr/deprecation-notice.md | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff --git a/ee/dtr/deprecation-notice.md b/ee/dtr/deprecation-notice.md index c6c11c0d9d..08b43d69db 100644 --- a/ee/dtr/deprecation-notice.md +++ b/ee/dtr/deprecation-notice.md @@ -8,15 +8,11 @@ This document outlines the functionalities or components within DTR that will be ### Enable Manifest List via the API -#### 2.5 +#### 2.5 and 2.6 -Since `v2.5`, it has been possible for repository admins to enable manifest lists when [creating a repository via the API](./reference/dtr/2.5/api/). You accomplish this by setting `enableManifestLists` to `true` when sending a POST request to the `/api/v0/repositories/{namespace}` endpoint. When enabled for a repository, any image that you push to an existing tag will be added to the manifest list for that tag. - -#### 2.6 - -Manifest lists are enabled for tags by default on any repository. There is no need to enable manifest lists using uthe API. +Since `v2.5`, it has been possible for repository admins to autogenerate manifest lists when [creating a repository via the API](./reference/dtr/2.5/api/). You accomplish this by setting `enableManifestLists` to `true` when sending a POST request to the `/api/v0/repositories/{namespace}` endpoint. When enabled for a repository, any image that you push to an existing tag will be appended to the list of manifests for that tag. `enableManifestLists` is set to false by default, which means pushing a new image to an existing tag will overwrite the manifest entry for that tag. #### 2.7 -The `v2.5` behavior and the `enableManifestLists` field will be removed in `v2.7`. Starting in `v2.7`, you can use the CLI command, `docker manifest` to [create and push a manifest list to any repository](./engine/reference/commandline/manifest/). +The above behavior and the `enableManifestLists` field will be removed in `v2.7`. Starting in `v2.7`, you can use the CLI command, `docker manifest`, to [create and push a manifest list to any repository](./engine/reference/commandline/manifest/).