Import chosen relation between two GitLab projects with NDJSON file
Problem
When importing projects with large relation (a lot of MRs or issues in a project), part of the relation items might not get imported. This happens when importing with export file (customer case). It might happen with Direct transfer as well. At the moment the only way to get all the items in a relation imported, is to import again and create a new project.
Proposed solution
We discussed possibility of re-importing chosen relation to an already existing project on the destination instance.
We will start with solution that will solve the problem also for the offline environments, that need to import with export files. Then follow up with Re-import chosen relation between between sourc... (#430789).
- Create a new Projects API endpoint to accept ndjson file only, to import specified relation to a chosen already existing on destination instance project.
- Create a new Groups API endpoint to accept ndjson file only, to import specified relation to a chosen already existing on destination instance group.
Using endpoints should append missing relation items, there should be no duplicates (e.g. MRs previously imported should be skipped).
Technical details
Documentation
New endpoints needs to be documented.
User documentation updated.
Follow-ups
- This issue focuses only on file import, but should lay the groundwork for similar behaviour in Direct Transfer.
- This issue focuses only on three key relations: issues, merge requests and CI pipelines.
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.