GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation allows making a POST request to the GitLab Geo API endpoint `/api/v4/geo/proxy_git_ssh/info_refs_upload_pack`. It is used to proxy Git SSH info refs upload pack requests through a Geo node, which is useful in GitLab Geo replication scenarios to handle Git SSH traffic between primary and secondary nodes.

Use Case Examples

  1. Proxying Git SSH info refs upload pack requests in a GitLab Geo setup to ensure Git operations are correctly routed and replicated across Geo nodes.
  2. Using the node to interact with the GitLab Geo API for advanced Git SSH proxying in distributed GitLab environments.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the request. If true, the request is sent without authentication.
baseUrl The base URL of the GitLab instance to which the request is sent. Defaults to https://gitlab.com.
Method The HTTP method to use for the request. Defaults to GET but can be set to POST, PUT, DELETE, HEAD, or PATCH.
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 operation, fixed to `/api/v4/geo/proxy_git_ssh/info_refs_upload_pack`.

Output

JSON

  • response - The JSON response returned from the GitLab Geo API after making the POST request to the proxy Git SSH info refs upload pack endpoint.

Dependencies

  • GitLab API authentication credentials

Troubleshooting

  • If authentication is required but skipped, the request may fail with authorization errors. Ensure the 'Skip Authentication' option is set correctly.
  • Incorrect baseUrl or path may lead to connection errors or 404 responses. Verify the GitLab instance URL and API path.
  • Improperly formatted request body according to the parameter schema can cause validation errors from the API.

Links

Discussion