diff options
Diffstat (limited to 'doc/development/bulk_import.md')
| -rw-r--r-- | doc/development/bulk_import.md | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/development/bulk_import.md b/doc/development/bulk_import.md index 0d9c7348915..b1fa4726b65 100644 --- a/doc/development/bulk_import.md +++ b/doc/development/bulk_import.md @@ -1,6 +1,6 @@ --- stage: Manage -group: Import +group: Import and Integrate info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments --- @@ -17,8 +17,6 @@ including projects, from one GitLab instance to another. ## Design decisions -### Overview - The following architectural diagram illustrates how the Group Migration works with a set of [ETL](#etl) Pipelines leveraging from the current [GitLab APIs](#api). @@ -37,13 +35,14 @@ idea is to have one ETL pipeline for each relation to be imported. ### API -The current [Project](../user/project/settings/import_export.md) and [Group](../user/group/settings/import_export.md) Import are file based, so they require an export -step to generate the file to be imported. +The current [project](../user/project/settings/import_export.md) and +[group](../user/group/import/index.md#migrate-groups-by-uploading-an-export-file-deprecated) imports are file based, so +they require an export step to generate the file to be imported. -GitLab Group migration leverages on [GitLab API](../api/rest/index.md) to speed the migration. +Group migration by direct transfer leverages the [GitLab API](../api/rest/index.md) to speed the migration. And, because we're on the road to [GraphQL](../api/graphql/index.md), -GitLab Group Migration will be contributing towards to expand the GraphQL API coverage, which benefits both GitLab +Group migration by direct transfer can contribute to expanding GraphQL API coverage, which benefits both GitLab and its users. ### Namespace |