GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves packages associated with a specific group in GitLab using the GitLab API v4. It is useful for scenarios where you need to list or manage packages within a GitLab group, such as fetching Maven, npm, or other package types for auditing, reporting, or automation purposes.

Use Case Examples

  1. Fetch all npm packages for a given GitLab group to analyze usage.
  2. Retrieve packages filtered by version or status to automate deployment workflows.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to connect to, defaulting to https://gitlab.com.
Method HTTP method to use for the API request, default is GET.
Parameter Schema Defines the parameters for the API call including path and query parameters such as group ID, pagination, sorting, filtering by package type, name, version, and status.
Query Parameters Collection of optional query parameters to filter and paginate the package list, including exclude_subgroups, page, per_page, order_by, sort, package_type, package_name, package_version, include_versionless, and status.
Path Parameters Collection of path parameters, specifically the group ID or URL-encoded path identifying the GitLab group.

Output

JSON

  • id - Unique identifier of the package.
  • name - Name of the package.
  • version - Version of the package.
  • type - Type of the package (e.g., npm, maven).
  • status - Current status of the package (e.g., default, hidden).
  • created_at - Timestamp when the package was created.
  • project_path - Path of the project associated with the package.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the group ID path parameter is correctly provided and URL-encoded if necessary.
  • Verify that the API authentication token is valid and has sufficient permissions to access group packages.
  • Check that query parameters are correctly formatted and valid according to the API specification.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid group ID), and 400 Bad Request (invalid query parameters). Resolving these involves correcting credentials, verifying group existence, and validating parameters respectively.

Links

Discussion