Gitlab Registy API: Allow URL-Encoded Registry ID

Problem to solve

Currently, all Tag operations in the registry api require a numerical ID for listing,deleting etc.: https://docs.gitlab.com/ee/api/container_registry.html#list-repository-tags

..while the project id will also accept a url-encoded string.

Same should apply for the repository_id.

For operations on registry tag api endpoint you currently have to:

  • use the list repositories endpoint to list all repositories
  • care about pagination ( so no simple curl )
  • filter out the element with the corresponding name and retrieve that id
  • finally use the id to list/delete tags...

Intended users

  • Sasha (Software Developer)
  • Devon (DevOps Engineer)
  • Sidney (Systems Administrator)

Further details

My use case

delete a tag when a pipeline finishes (we're using semver AND CI_PIPELINE_IID as tags to ensure consistency between parallel pipelines, the CI_PIPELINE_IID tag is obsolete when the pipeline finishes.

Proposal

allow url-encoded repository_id. The url-encoded name should also be unique, afaik.

Permissions and Security

Documentation

Testing

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

What is the type of buyer?

Links / references

Assignee Loading
Time tracking Loading