GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation authorizes access to a specific Conan package file within a GitLab project using the GitLab API. It is designed to handle PUT requests to the GitLab API endpoint that manages Conan package files, allowing users to authorize the export of a particular file version of a Conan package. This is useful in scenarios where automated workflows need to manage package files in GitLab repositories, such as CI/CD pipelines or package management automation.

Use Case Examples

  1. Automating authorization of Conan package files in a GitLab project during a CI/CD pipeline.
  2. Managing access control for specific versions of Conan packages in a GitLab repository programmatically.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method used for the request, which is PUT for this operation.
Path Parameters Parameters required in the URL path to identify the project and specific Conan package file to authorize.

Output

JSON

  • statusCode - HTTP status code of the API response.
  • body - The response body from the GitLab API, typically containing authorization details or confirmation.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure all required path parameters are correctly provided and URL-encoded if necessary.
  • Verify that the authentication token has sufficient permissions to authorize package files in the specified project.
  • Check that the file_name parameter matches one of the allowed file names exactly.
  • Common errors include 401 Unauthorized (authentication issues), 404 Not Found (incorrect project or package details), and 400 Bad Request (invalid parameters).

Links

Discussion