GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves detailed information about a specific Conan package from the GitLab API. It is useful for users who need to access metadata or details of a Conan package hosted on GitLab, such as package version, username, and channel. Practical applications include automating package management workflows, integrating package data into CI/CD pipelines, or auditing package versions.

Use Case Examples

  1. Fetch details of a Conan package named 'my-package' with version '1.0' under the username 'my-group+my-project' and channel 'stable' from GitLab.
  2. Use the node to automate retrieval of package metadata for deployment or analysis.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making the API request.
Authentication Type of authentication to use, defaulting to GitLab API key.
baseUrl Base URL of the GitLab instance to send the request to, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Parameter Schema Schema defining the required path parameters for the API call, including package name, version, username, and channel.
Request Body Schema Schema for the request body, not used in this GET operation.
Request Path API endpoint path template with placeholders for package details.
Path Parameters Collection of path parameters specifying the package name, version, username, and channel to identify the Conan package.

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 associated with the package.
  • channel - Channel of the package (e.g., stable, testing).
  • metadata - Additional metadata and details about the package retrieved from GitLab.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the path parameters (package_name, package_version, package_username, package_channel) are correctly set and match the package details in GitLab.
  • If authentication is enabled, verify that the GitLab API key credential is valid and has sufficient permissions to access the package data.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure the URL is correct.
  • Common error messages include 404 Not Found if the package does not exist or 401 Unauthorized if authentication fails. Verify parameters and credentials accordingly.

Links

Discussion