Skip to content

Take migration status into account for size

Jeff Pearcerequested to merge
(removed):359127-migration-status into master

What does this MR do and why?

This addresses #359127 (closed), by allowing size calculation if a repository has migration_state of 'import_done'.

How to set up and validate locally

  1. Follow the steps in !80412 (merged) for setting up the container registry
  2. Build and upload a Docker image to a project's repository. Visit the repo page to get the repository id
  3. curl (or postman) http://gdk.test:3000/api/v4/registry/repositories/<repository-id>?size=true
  4. observe whether "size" in the response is null or not. If null, the size calculation is being bypassed.

Test cases. Use gdk psql to change values for the repository in the container_repositories table as follows:

  1. change migration_status to "default" and created_at to any date before Nov 4, 2021. API request above should return a null size
  2. change migration_status to "import_done" and created_at to any date before Nov 4, 2021. API request above should NOT return a null size
  3. change migration_status to "default" and created_at to any date after Nov 4, 2021. API request above should NOT return a null size

MR acceptance checklist

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

Related to #359127 (closed)

Merge request reports