GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation authorizes access to a specific Conan package file in a GitLab repository using the GitLab API. It is useful for managing and securing access to Conan package files stored in GitLab, particularly in CI/CD pipelines or automated workflows where package file authorization is required before download or usage.

Use Case Examples

  1. Authorizing access to a Conan package file named 'conaninfo.txt' for version '1.0' of a package 'my-package' under a specific user and channel.
  2. Automating the authorization process for Conan package files in a GitLab project to ensure secure package management.

Properties

Name Meaning
Skip Authentication If true, the node will skip authentication when making the API request.
Authentication The authentication method used for the API request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method used for the request, default is PUT.
Path Parameters Parameters required to specify the exact Conan package file to authorize, including package name, version, username, channel, recipe revision, Conan package reference, package revision, and file name.

Output

JSON

  • statusCode - HTTP status code of the authorization request response.
  • body - Response body containing authorization details or error messages.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure all required path parameters are correctly provided; missing or incorrect parameters will cause request failures.
  • Verify that the GitLab API key credential has sufficient permissions to authorize package files.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (incorrect package or file details), and 403 Forbidden (insufficient permissions).

Links

Discussion