Skip to content

Change container registry copy expiration policy to cleanup policies

What does this MR do and why?

In the container registry, we refer to the same feature in different ways.

Be more consistent in the way we name cleanup policies.

Screenshots or screen recordings

Page Before After
Admin settings Screenshot_2023-03-29_at_11.28.33_pm Screenshot_2023-03-29_at_11.15.14_pm
Project settings Screenshot_2023-03-29_at_11.26.11_pm Screenshot_2023-03-29_at_11.12.57_pm
Project cleanup policy settings Screenshot_2023-03-29_at_11.26.27_pm Screenshot_2023-03-29_at_11.12.48_pm
Container registry list Screenshot_2023-03-29_at_11.26.38_pm Screenshot_2023-03-29_at_11.14.06_pm
Container registry list (cleanup disabled) Screenshot_2023-03-29_at_11.28.02_pm Screenshot_2023-03-29_at_11.13.11_pm

How to set up and validate locally

  1. Setup & enable Container Registry https://gitlab.com/gitlab-org/gitlab-development-kit/-/blob/main/doc/howto/registry.md
  2. Verify text is updated in admin settings, project settings and container registry list page.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Closes #358886 (closed)

Edited by Rahul Chanila

Merge request reports