GitLab API

GitlabTool
Join our community

Actions1000

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 to access Conan packages in a GitLab project before deploying packages.
  2. Automate permission verification for users managing Conan packages in a project.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication to use, default is GitLab API key.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Path Parameters Parameters to be included in the request path, specifically the project ID or URL-encoded path.

Output

JSON

  • status - HTTP response status code indicating the result of the credentials check.
  • body - Response body containing details about the credentials check result.

Dependencies

  • GitLab API key credential

Troubleshooting

  • If authentication is skipped but the API requires it, the request will fail with an authentication error. Ensure the 'Skip Authentication' option is set correctly.
  • If the project ID or path is incorrect or missing, the API will return an error indicating the resource was not found. Verify the 'Id' path parameter is accurate.
  • Common error messages include 401 Unauthorized (invalid or missing credentials) and 404 Not Found (invalid project ID). Resolving these involves checking credentials and project identifiers.

Links

Discussion