GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation authorizes access to a specific Conan package file within a GitLab project using the GitLab API. It is useful for managing and securing access to Conan package files in CI/CD pipelines or automated workflows involving package management in GitLab projects. For example, it can be used to programmatically authorize access to package files like conanfile.py or conan_package.tgz for a given project and package version.

Use Case Examples

  1. Automate authorization of Conan package files in a GitLab project during a CI/CD pipeline.
  2. Manage access control for specific package files in a GitLab-hosted Conan repository.

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 for GitLab.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to GET but can be PUT for this operation.
Path Parameters Parameters required in the URL path to identify the project and package file to authorize.

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 and URL-encoded if necessary.
  • Verify that the GitLab API key credential has sufficient permissions to authorize package files.
  • Check the baseUrl is correct for the GitLab instance being accessed.
  • Common errors include 401 Unauthorized (invalid or missing API key), 404 Not Found (incorrect project ID or package details), and 400 Bad Request (invalid parameters).

Links

Discussion