GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation authorizes a RubyGem package for a specific project in GitLab by sending a POST request to the GitLab API endpoint `/api/v4/projects/{id}/packages/rubygems/api/v1/gems/authorize`. It is useful for automating package authorization workflows within GitLab projects, such as when managing RubyGem packages in CI/CD pipelines or package registries.

Use Case Examples

  1. Automate authorization of RubyGem packages for a project in GitLab during deployment.
  2. Integrate RubyGem package authorization into a CI/CD pipeline to ensure packages are authorized before publishing.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the API request.
Authentication The authentication method used for the API request, hidden unless Skip Authentication is false.
baseUrl The base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, defaulting to GET but can be set to POST, PUT, DELETE, HEAD, or PATCH.
Path Parameters The path parameters for the API request, specifically the project ID or URL-encoded path required to identify the project in GitLab.

Output

JSON

  • statusCode - The HTTP status code returned by the API request.
  • body - The JSON response body from the API request, containing authorization details for the RubyGem package.

Dependencies

  • GitLab API credentials for authentication

Troubleshooting

  • Ensure the project ID provided in the path parameters is correct and accessible with the provided credentials.
  • If authentication is skipped, the API request may fail due to lack of authorization.
  • Verify that the baseUrl is correctly set to the GitLab instance URL if using a self-hosted GitLab server.
  • Check that the HTTP method is set to POST for this operation as required by the API endpoint.

Links

Discussion