zuul-jobs/roles/remove-registry-tag
Ian Wienand 7bbe8f5b0d
remove-registry-tag: no_log assert
Just to be sure, add no_log here.  Since the actual authenticated call
is no_log too; if this fails you at least know you didn't get the
credentials layout right which narrows down the problems the actual
call might be facing.

Change-Id: Ic7174c10f4e693f6a2c0554dc66ea22fd28d678f
2023-04-05 07:38:54 +10:00
..
defaults remove-registry-tag: role to delete tags from registry 2023-04-04 09:53:18 +10:00
tasks remove-registry-tag: no_log assert 2023-04-05 07:38:54 +10:00
README.rst remove-registry-tag: role to delete tags from registry 2023-04-04 09:53:18 +10:00

Remove tags from registry

This role creates a generic interface for removing tags from a container registry. The OCI distribution API (implemented essentially all registries) does specify a tag deletion endpoint, but as at 2023-03 essentially no registries implement it. This means practically we must talk to the per-registry API directly to remove tags. The methods to delete tags are generally similar across registries, but differ slightly in endpoint names, etc.

This role can run in two modes; either removing a single specific tag, or it can run a cleanup process removing all tags that match a given prefix and have not been modified in a given amount of time.

For public registries this role should guess the API from the repository name. If you are running against a private registry, you will need to explicitly specify the API type and URL prefix to communicate to using arguments below.

Role Variables