Leverage the GitLab API to define and update Docker tag expiration policies

Problem to solve

#15398 (closed) introduced a new UI element that allowed project owners to define an expiration policy for Docker images hosted in the GitLab Container Registry. However, for organizations with many projects, this is an inefficient method of setting and updating these policies. We should allow users to leverage the GitLab API to define and update these policies, so they don't have to rely on the user interface.

Intended users

• Sidney (Systems Administrator)

Further details

Proposal

Expand the Container Registry API to include the ability to define, update and delete Docker tag expiration policies.

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references