GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves details of a specific project repository storage move from GitLab using the GitLab API. It is useful for users who need to track or manage storage moves of project repositories within GitLab, such as verifying the status or metadata of a storage move by its unique ID.

Use Case Examples

  1. A DevOps engineer wants to check the status of a repository storage move by providing its ID to ensure the move completed successfully.
  2. A project manager needs to audit repository storage moves for compliance and uses this node to fetch detailed information about each move.

Properties

Name Meaning
Skip Authentication Option to bypass authentication for the request, useful for public or unauthenticated access.
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 used for the API request, defaulting to GET.
Path Parameters Collection of path parameters required for the API request, specifically the repository_storage_move_id which identifies the storage move to retrieve.

Output

JSON

  • id - The unique identifier of the repository storage move.
  • source_storage_name - The name of the source storage from which the repository is being moved.
  • destination_storage_name - The name of the destination storage to which the repository is being moved.
  • state - The current state of the storage move (e.g., 'finished', 'failed').
  • created_at - Timestamp when the storage move was created.
  • updated_at - Timestamp when the storage move was last updated.
  • project_id - The ID of the project associated with the repository storage move.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the repository_storage_move_id path parameter is provided and is a valid integer; missing or invalid IDs will cause request failures.
  • Authentication errors may occur if the GitLab API key is missing, invalid, or lacks sufficient permissions; verify the API key and its scopes.
  • Network or base URL misconfiguration can lead to connection errors; confirm the baseUrl is correct and accessible.
  • API rate limits or GitLab server issues may cause request failures; check GitLab status and retry later.

Links

Discussion