GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation checks user credentials for Conan packages in a specific GitLab project using the GitLab API. It is useful for verifying if a user has the necessary permissions to access or manage Conan packages within a project. For example, it can be used in CI/CD pipelines or automation workflows to validate user access before performing package-related actions.

Use Case Examples

  1. Check if a user has valid credentials for Conan packages in a GitLab project before allowing package upload.
  2. Verify user permissions for Conan packages in a project as part of an automated security audit.

Properties

Name Meaning
Skip Authentication If true, the node skips authentication for the request.
Authentication The authentication method used for the 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 used for the request, such as GET, POST, PUT, DELETE, HEAD, or PATCH.
Path Parameters The path parameters for the API request, specifically the project ID or URL-encoded path to identify the GitLab project.

Output

JSON

  • statusCode - HTTP status code of the API response indicating success or failure of the credentials check.
  • body - The JSON response body from the GitLab API containing details about the credentials check result.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible.
  • Verify that the GitLab API token has sufficient permissions to check Conan package credentials.
  • If skipping authentication, the request may fail due to lack of authorization.
  • Common error messages include 401 Unauthorized (invalid or missing token) and 404 Not Found (invalid project ID).

Links

Discussion