GitLab API

GitlabTool
Join our community

Actions1000

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-related actions, 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. A DevOps engineer uses this node to verify that the credentials for accessing GitLab Conan packages are valid before triggering a package upload.
  2. A developer integrates this node in an automation workflow to check if the current user has the necessary permissions to access Conan packages in a GitLab project.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip the authentication process.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request (GET, POST, PUT, DELETE, HEAD, PATCH).
Parameter Schema Hidden property for the parameter schema of the request, specific to this operation.
Request Body Schema Hidden property for the request body schema, specific to this operation.
Request Path The API endpoint path for checking user credentials in the Conan packages context.

Output

JSON

  • statusCode - HTTP status code returned by the API request.
  • responseBody - The JSON response body from the API, indicating the result of the credentials check.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • If authentication fails, ensure the GitLab API credentials are correctly configured and have the necessary permissions.
  • Check the baseUrl to confirm it points to the correct GitLab instance.
  • Verify that the HTTP method is appropriate for the operation, typically GET for this credentials check.

Discussion