GitLab Migration - Migrate a subgroup via API
Problem to solve
Currently, we only allow migrations of top-level groups. This limitation was introduced to allow smaller iterations toward the final solution. However, users have a need to migrate groups, whether they are top-level, or subgroups.
In order to migrate a subgroup, the user currently has to do a workaround, such as:
- promote (move) a subgroup into a top-level group - this may not always be an option due to instance and user permissions
- use the old Group export/import process, which we want to deprecate in favor of GitLab Migration
Proposal
As a first step in allowing users to easily migrate groups of any level, we will allow the user to migrate a subgroup via the API.
The API will accept any group (whether top-level, or subgroup) to start the migration.
Iterations
This issue is a part of a larger feature - #267952, which was broken down into these iterations:
-
👣 As a first iteration, we can allow the ability to migrate a subgroup (not a top-level group) via the API. - THIS ISSUE -
👣 Allow the user to migrate a subgroup via the UI - #350490 -
👣 Allow the user to migrate multiple subgroups via the UI - future issue -
👣 Potential future iterations: allow the user to select any mix of top-level groups, subgroups, or projects to migrate via the UI - future issues
Solution
Per this comment, the API already supports subgroups. This issue was closed as obsolete (already works).
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.