GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation checks user credentials for accessing Conan packages in a specific GitLab project via the GitLab API. It is useful for verifying if a user has the necessary permissions to interact with 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 operations.

Use Case Examples

  1. Check if a user has valid credentials to access Conan packages in a GitLab project before downloading or uploading packages.
  2. Validate user permissions programmatically in an automation workflow to ensure secure package management.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated access scenarios.
Authentication Type of authentication used for the request, defaulting to GitLab API token authentication.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method used for the request, default is GET.
Path Parameters Parameters included in the request path, specifically the project ID or URL-encoded path to identify the GitLab project.

Output

JSON

  • response - The API response indicating the result of the credentials check, typically including status and user permission details.

Dependencies

  • GitLab API token credential

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible.
  • Verify that the GitLab API token used for authentication has sufficient permissions to check user credentials for the project.
  • If skipping authentication, confirm that the GitLab instance allows unauthenticated access to this endpoint, otherwise the request will fail.
  • Common error messages include 401 Unauthorized (invalid or missing token) and 404 Not Found (incorrect project ID). Resolving these involves checking token validity and project existence.

Links

Discussion