GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation retrieves details of a specific project repository storage move in GitLab by its ID. It is useful for users who want to track or manage the status and information of repository storage moves within their GitLab projects. For example, a DevOps engineer might use this to monitor the progress of repository storage migration tasks.

Use Case Examples

  1. Retrieve details of a repository storage move by providing its unique ID to check its status and metadata.
  2. Use in automation workflows to fetch repository storage move information for reporting or auditing purposes.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated access scenarios.
Authentication Type of authentication to use for the request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, defaulting to GET.
Path Parameters Parameters to be included in the request path, 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., pending, in progress, completed).
  • 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

Troubleshooting

  • Ensure the repository_storage_move_id path parameter is provided and valid; missing or incorrect IDs will cause errors.
  • Authentication errors may occur if the GitLab API key credential is missing or invalid; verify credentials are correctly configured.
  • Network or baseUrl issues can cause request failures; confirm the baseUrl is correct and accessible.
  • HTTP method should be GET for this operation; using other methods may result in unexpected behavior or errors.

Links

Discussion