GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation retrieves detailed information about a specific Conan package hosted on GitLab. It is useful for developers and DevOps teams who need to programmatically access package metadata such as version, username, and channel from GitLab's Conan package registry. For example, it can be used to automate package version checks or integrate package data into CI/CD pipelines.

Use Case Examples

  1. Fetch details of a Conan package named 'my-package' with version '1.0', owned by 'my-group+my-project', and in the 'stable' channel from GitLab.
  2. Automate retrieval of package metadata to verify package versions before deployment.

Properties

Name Meaning
Skip Authentication Option to bypass authentication when making the API request.
Authentication Type of authentication used for the API request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method HTTP method used for the API request, defaulting to GET.
Path Parameters Parameters used to specify the Conan package details in the API path, including package name, version, username, and channel.

Output

JSON

  • id - Unique identifier of the Conan package.
  • name - Name of the Conan package.
  • version - Version of the Conan package.
  • username - Username or group/project owning the package.
  • channel - Channel of the Conan package.
  • metadata - Additional metadata and details about the Conan package.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the path parameters (package_name, package_version, package_username, package_channel) are correctly provided and not empty to avoid 404 errors.
  • If authentication is enabled, verify that the GitLab API key credential is valid and has sufficient permissions to access the package registry.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure the URL is correct and accessible.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (package not found), and 400 Bad Request (invalid parameters). Resolving these involves verifying credentials, parameters, and endpoint URLs.

Links

Discussion