GitLab API

GitlabTool

Actions1000

Overview

This node operation authorizes access to a NuGet package feed for a specific project in GitLab. It is useful for automating the process of granting or managing authorization to NuGet packages hosted within GitLab projects, typically in CI/CD pipelines or package management workflows.

Use Case Examples

  1. Automate authorization for NuGet package feeds in a GitLab project during deployment.
  2. Integrate GitLab NuGet package authorization into a custom automation workflow to manage package access.

Properties

Name Meaning
Skip Authentication If set to true, the node skips the authentication step, allowing unauthenticated requests.
Authentication Specifies the authentication method to use, defaulting to GitLab API authentication. Hidden if Skip Authentication is true.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, defaulting to GET. Options include GET, POST, PUT, DELETE, HEAD, PATCH.
Path Parameters Parameters to be included in the request path, specifically the project ID or URL-encoded path required for the authorization endpoint.

Output

JSON

  • statusCode - HTTP response status code from the authorization request
  • body - Response body content from the authorization request, typically containing authorization details or error messages

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible with the authenticated user.
  • Verify that the GitLab API credentials are valid and have sufficient permissions to authorize NuGet package access.
  • Check the baseUrl to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages may include 401 Unauthorized if authentication fails, 404 Not Found if the project ID is invalid, or 403 Forbidden if permissions are insufficient.

Discussion