GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves Composer package information from a specific GitLab group using the GitLab API. It is useful for developers or DevOps engineers who need to fetch details about Composer packages hosted within a GitLab group, such as package metadata or version information. For example, it can be used to automate dependency management or integrate package data into CI/CD pipelines.

Use Case Examples

  1. Fetch details of a Composer package named 'my-composer-package' from a GitLab group identified by its ID or URL-encoded path.
  2. Automate retrieval of package metadata for auditing or reporting purposes within a GitLab-hosted project.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request (boolean). Defaults to false.
Authentication The authentication method used, defaulting to GitLab API key authentication. Hidden unless 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, default is GET.
Query Parameters.package_name The Composer package name to retrieve information for.
Path Parameters.id The ID or URL-encoded path of the GitLab group from which to retrieve the package.

Output

JSON

  • id - The ID or URL-encoded path of the GitLab group.
  • package_name - The name of the Composer package retrieved.
  • package_data - The detailed information about the Composer package returned by the GitLab API.

Dependencies

  • GitLab API key credential for authentication unless Skip Authentication is enabled.

Troubleshooting

  • Ensure the GitLab group ID or path is correctly URL-encoded and valid to avoid 404 errors.
  • Verify the package_name query parameter is correctly specified and matches an existing Composer package in the group.
  • Authentication errors may occur if the API key credential is missing, invalid, or lacks sufficient permissions.
  • Network or baseUrl misconfiguration can cause connection failures; verify the baseUrl is correct for your GitLab instance.

Links

Discussion