GitLab API

GitlabTool

Actions905

Overview

This node operation performs a POST request to the GitLab Geo API endpoint `/api/v4/geo/proxy_git_ssh/info_refs_upload_pack`. It is used to interact with the GitLab Geo proxy for Git SSH info refs upload pack functionality, typically for advanced Git operations in a Geo-replicated GitLab environment. This can be useful for synchronizing Git data across Geo nodes or handling Git SSH requests through the Geo proxy.

Use Case Examples

  1. Synchronize Git repository data between Geo nodes in a GitLab setup.
  2. Handle Git SSH info refs upload pack requests via the Geo proxy for distributed Git operations.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the request.
Authentication The authentication method to use for the request, typically a GitLab API key credential.
baseUrl The base URL of the GitLab instance to which the request is sent, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to POST for this operation.
Parameter Schema The schema defining the parameters for the POST request body, required for this operation.
Request Body Schema The schema defining the structure of the request body for the POST operation.
Request Path The API endpoint path for the POST request, fixed to `/api/v4/geo/proxy_git_ssh/info_refs_upload_pack`.

Output

JSON

  • response - The JSON response from the GitLab Geo API for the info refs upload pack request.

Dependencies

  • Requires a GitLab API key credential for authentication unless skipping authentication is enabled.

Troubleshooting

  • If authentication is skipped but the GitLab instance requires authentication, the request will fail with an authorization error. Ensure the correct API key credential is provided or skip authentication only if allowed.
  • Incorrect baseUrl or path may lead to connection errors or 404 responses. Verify the GitLab instance URL and API endpoint path.
  • Malformed request body according to the parameter schema can cause validation errors from the API. Ensure the request body matches the expected schema.

Links

Discussion