Fix docker image retag

The missing "." from the content-type headers was causing us
to downgrade image manifests from v1 to to v2 when promoting them.
That can cause problems since many tools no longer support v1
manifests.

Notably, the docker registry is one of them.

Change-Id: I35a5d29933669b80b49578587ebe6db8e13e62ad
This commit is contained in:
James E. Blair 2019-03-01 15:55:24 -08:00
parent 9c0d25f349
commit 9cbb8c0ac6
1 changed files with 2 additions and 2 deletions

View File

@ -4,7 +4,7 @@
url: "https://registry.hub.docker.com/v2/{{ image.repository }}/manifests/change_{{ zuul.change }}_{{ image_tag }}"
status_code: 200
headers:
Accept: "application/vnd.docker.distribution.manifestv2+json"
Accept: "application/vnd.docker.distribution.manifest.v2+json"
Authorization: "Bearer {{ token.json.token }}"
return_content: true
register: manifest
@ -16,7 +16,7 @@
status_code: 201
body: "{{ manifest.content | string }}"
headers:
Content-Type: "application/vnd.docker.distribution.manifestv2+json"
Content-Type: "application/vnd.docker.distribution.manifest.v2+json"
Authorization: "Bearer {{ token.json.token }}"
- name: Delete the current change tag
no_log: true