Migrate Generic Packages Repository
Overview
A customer is using the generic package registry and will require that it be migrated from their SaaS instance to a new self-managed instance.
Tasks
-
Create API wrapper class to interface with our package registry API -
Create an API wrapper class to interface with our Generic Package Regsitry. Specifically we need the publish and download endpoints wrapped in the class -
Create a generic_packages.py
client class undercongregate/migration/gitlab
covering the migration process of:- Listing the generic packages of a project - For each package - Download the package to the VM - Upload the package to the destination project package registry - Delete the package from the VM
-
Add the generic package migration client to our post-migration step in the GitLab migrate client -
Update docs if needed (workflow, runbooks, README, migration metrics, etc.)
Acceptance Criteria
-
Existing UTs pass locally -
100% code coverage on new code
@gitlab-org/professional-services-automation/tools/migration
Edited by Michael Leopard