GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves the digest information of a specific Conan package from the GitLab Packages Conan API (v1). It is useful for users who want to verify or inspect the digest of a Conan package stored in a GitLab repository, which can help ensure package integrity and authenticity. For example, a developer or DevOps engineer might use this operation to programmatically fetch the digest of a Conan package version to validate it before deployment or integration.

Use Case Examples

  1. Fetch the digest of a Conan package named 'my-package' with version '1.0' under the username 'my-group+my-project' and channel 'stable' to verify its integrity.
  2. Use the operation to automate the retrieval of package digests for auditing or compliance purposes in a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request (boolean). Defaults to false.
Authentication The authentication method used for the API request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance. Defaults to https://gitlab.com.
Method The HTTP method used for the request. Defaults to GET.
Path Parameters Parameters required in the request path to identify the specific Conan package digest to retrieve. Includes package_name, package_version, package_username, package_channel, and conan_package_reference.

Output

JSON

  • digest - The digest information of the specified Conan package.
  • package_name - The name of the Conan package.
  • package_version - The version of the Conan package.
  • package_username - The username or group/project owning the package.
  • package_channel - The channel of the package.
  • conan_package_reference - The unique Conan package ID.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure all required path parameters (package_name, package_version, package_username, package_channel, conan_package_reference) are correctly provided and non-empty.
  • Verify that the GitLab API authentication credential is valid and has sufficient permissions to access the package data.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages may include 401 Unauthorized (authentication issues), 404 Not Found (incorrect package details or permissions), and 400 Bad Request (invalid parameters). Resolving these involves verifying credentials, parameters, and API endpoint correctness.

Links

Discussion