GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation allows transferring a GitLab group to a new namespace by making a POST request to the GitLab API endpoint `/api/v4/groups/{id}/transfer`. It is useful for automating group management tasks such as reorganizing group ownership or structure within GitLab.

Use Case Examples

  1. Transferring a GitLab group with a specific ID to a new namespace programmatically.
  2. Automating group ownership changes in GitLab as part of a DevOps workflow.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated API calls.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method HTTP method to use for the API request, defaulting to GET but can be set to POST, PUT, DELETE, HEAD, or PATCH.
Path Parameters Parameters to be included in the request path, specifically the group ID to transfer.

Output

JSON

  • id - The ID of the transferred group.
  • name - The name of the transferred group.
  • path - The path of the transferred group.
  • full_path - The full path of the transferred group after transfer.
  • parent_id - The ID of the new parent namespace after transfer.
  • visibility - The visibility level of the group.
  • web_url - The web URL of the group in GitLab.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the group ID provided in the path parameters is valid and exists in GitLab.
  • Verify that the API key used for authentication has sufficient permissions to transfer groups.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages include 404 Not Found if the group ID does not exist, 403 Forbidden if permissions are insufficient, and 400 Bad Request if the request body is malformed.

Links

Discussion