GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation performs a bulk import of entities into a GitLab instance using the GitLab API v4. It is useful for migrating groups or projects from a source GitLab instance to a destination namespace within another GitLab instance. Typical use cases include migrating multiple projects or groups in bulk, preserving memberships, and specifying destination slugs or namespaces for the imported entities.

Use Case Examples

  1. Migrating multiple projects from a source GitLab instance to a new namespace in a destination GitLab instance.
  2. Bulk importing groups including nested projects and memberships to a GitLab server.

Properties

Name Meaning
Skip Authentication If set to true, the node skips using authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to which the bulk import request is sent.
Method The HTTP method used for the request, default is POST for bulk imports.
Parameter Schema Defines the form data parameters required for the bulk import, including source URL, access token, entity types, source paths, destination namespaces, slugs, and migration options.
Request Path The API endpoint path for the bulk import operation, fixed as /api/v4/bulk_imports.

Output

JSON

  • id - The unique identifier of the bulk import job created.
  • status - The current status of the bulk import job.
  • created_at - Timestamp when the bulk import job was created.
  • updated_at - Timestamp when the bulk import job was last updated.
  • entities - Details about the entities being imported, including their source and destination information.

Dependencies

  • GitLab API v4

Troubleshooting

  • Ensure the access token provided has sufficient permissions to perform bulk imports on the source GitLab instance.
  • Verify that the source URL and entity paths are correctly specified and accessible.
  • Check that the destination namespace exists and the user has rights to import entities there.
  • Common errors include authentication failures, invalid entity paths, or insufficient permissions, which can be resolved by verifying credentials and input parameters.

Links

Discussion