GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves details of a specific snippet repository storage move from the GitLab API. It is useful for users who need to track or manage storage moves of snippet repositories within GitLab, such as DevOps engineers or project administrators. For example, it can be used to fetch the status or metadata of a storage move by providing its unique ID.

Use Case Examples

  1. Fetch details of a snippet repository storage move by its ID to monitor migration progress.
  2. Retrieve metadata about a specific storage move for auditing or reporting purposes.

Properties

Name Meaning
Skip Authentication Option to bypass authentication for the request.
Authentication Type of authentication used, defaulting to GitLab API key.
baseUrl Base URL of the GitLab instance to send requests to.
Method HTTP method to use for the request, default is GET.
Parameter Schema Schema defining the path parameter for the repository storage move ID.
Request Body Schema Schema for the request body, null for this GET operation.
Request Path API endpoint path with placeholder for repository storage move ID.
Path Parameters Collection of path parameters including the repository_storage_move_id which is required to identify the specific storage move.

Output

JSON

  • id - The unique identifier of the snippet repository storage move.
  • source_storage - The source storage location of the snippet repository.
  • destination_storage - The destination storage location for the snippet repository.
  • state - Current state or status of the storage move.
  • created_at - Timestamp when the storage move was created.
  • updated_at - Timestamp when the storage move was last updated.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the repository_storage_move_id path parameter is provided and valid; missing or incorrect ID will cause errors.
  • Authentication errors may occur if the GitLab API key is missing or invalid; verify credentials.
  • Network or baseUrl misconfiguration can lead to connection failures; confirm the baseUrl is correct for your GitLab instance.

Links

Discussion