GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation authorizes access to a specific Conan package file within a GitLab project. It is useful for managing permissions and ensuring secure access to package files in a CI/CD pipeline or package management workflow. For example, it can be used to authorize downloading or uploading files like conanfile.py or conan_package.tgz for a given project and package version.

Use Case Examples

  1. Authorize access to the conanfile.py of a Conan package version 1.0 in a GitLab project with ID '123'.
  2. Authorize access to the conan_package.tgz file for a specific package channel and recipe revision in a GitLab project.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated access.
Authentication Type of authentication used, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, defaulting to GET. Options include GET, POST, PUT, DELETE, HEAD, PATCH.
Path Parameters Parameters required in the API path to identify the project and package file to authorize access to.

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

Troubleshooting

  • Ensure all required path parameters are correctly provided and URL-encoded if necessary.
  • Verify that the GitLab API key credential is valid and has sufficient permissions to authorize package file access.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages may include 401 Unauthorized if authentication fails, 404 Not Found if the project or package file does not exist, and 403 Forbidden if the user lacks permission.

Links

Discussion