GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation allows users to authorize a specific Maven package file within a GitLab project by sending a PUT request to the GitLab API endpoint `/api/v4/projects/{id}/packages/maven/*path/{file_name}/authorize`. It is useful for managing access control and permissions for Maven package files in GitLab projects, enabling automation of package authorization workflows.

Use Case Examples

  1. Automate authorization of Maven package files in a CI/CD pipeline.
  2. Manage access permissions for Maven packages in GitLab projects programmatically.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, 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 for the API path including project ID and Maven package file name.

Output

JSON

  • status - HTTP response status indicating the result of the authorization request.
  • data - Response data from the GitLab API regarding the authorization of the Maven package file.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID and file name are correctly specified and URL-encoded if necessary.
  • Verify that the GitLab API key has sufficient permissions to authorize Maven package files.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (incorrect project ID or file name), and 403 Forbidden (insufficient permissions).

Links

Discussion