GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation checks user credentials for Conan packages in GitLab via the GitLab API. It is useful for verifying authentication status before performing package management tasks, ensuring that the user has valid access rights. For example, it can be used in CI/CD pipelines to validate credentials before uploading or downloading Conan packages.

Use Case Examples

  1. Verify user credentials for Conan package management in GitLab before executing package upload.
  2. Check if the current user has valid authentication to access Conan packages in a GitLab project.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip the authentication process.
Authentication The authentication method used for the GitLab API, hidden unless Skip Authentication is false.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the API request, default is GET.
Parameter Schema Hidden property for the parameter schema of the operation, not user-editable.
Request Body Schema Hidden property for the request body schema of the operation, not user-editable.
Request Path The API endpoint path for checking user credentials, fixed to /api/v4/packages/conan/v1/users/check_credentials.

Output

JSON

  • statusCode - HTTP status code of the API response
  • body - The JSON response body containing the result of the credentials check

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • If authentication fails, ensure the GitLab API token is valid and has the necessary permissions to access Conan packages.
  • Check the baseUrl property if using a self-hosted GitLab instance to ensure it points to the correct URL.
  • HTTP errors such as 401 Unauthorized indicate invalid or missing credentials; verify the API token and authentication settings.

Links

Discussion