GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves Composer packages for a specific group from the GitLab API (version 4). It is useful for automating the process of fetching package information from a GitLab group, which can be beneficial in CI/CD pipelines, package management automation, or integration workflows involving GitLab package registries.

Use Case Examples

  1. Fetch all Composer packages for a given GitLab group by specifying the group's ID or URL-encoded path.
  2. Use this operation to monitor or audit packages published within a GitLab group.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
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.
Path Parameters Parameters included in the API request path, specifically the 'id' which is the ID or URL-encoded path of the GitLab group whose Composer packages are being retrieved.

Output

JSON

  • id - The unique identifier of the Composer package.
  • name - The name of the Composer package.
  • version - The version of the Composer package.
  • package_type - The type of the package, e.g., composer.
  • created_at - Timestamp when the package was created.
  • updated_at - Timestamp when the package was last updated.
  • project_id - The ID of the project associated with the package.
  • group_id - The ID of the group to which the package belongs.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the 'id' path parameter is correctly set to the group's ID or URL-encoded path; otherwise, the API request will fail.
  • If authentication is enabled, verify that the GitLab API key credential is valid and has sufficient permissions to access the group's packages.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure the URL is correct.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (invalid group ID or path), and 403 Forbidden (insufficient permissions). Resolving these involves verifying credentials, permissions, and input parameters.

Links

Discussion