GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves Debian package information from a specific GitLab project using the GitLab API. It is useful for automating the fetching of Debian package metadata for a given project, distribution, component, and architecture. For example, it can be used in CI/CD pipelines to verify package availability or to integrate package data into other systems.

Use Case Examples

  1. Fetch Debian package metadata for a project with ID '123' for the 'my-distro' distribution, 'main' component, and 'binary-amd64' architecture.
  2. Automate retrieval of Debian package lists from GitLab projects to monitor package updates.

Properties

Name Meaning
Skip Authentication Whether to skip authentication when making the API request.
Authentication The authentication method to use for the API request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to send the API request to, defaulting to https://gitlab.com.
Method The HTTP method to use for the API request, defaulting to GET.
Query Parameters Query parameters for the API request, specifically the 'distribution' parameter representing the Debian Codename or Suite.
Path Parameters Path parameters for the API request including 'id' (project ID or URL-encoded path), 'component' (Debian Component), and 'architecture' (Debian Architecture).

Output

JSON

  • id - The ID or URL-encoded path of the project.
  • distribution - The Debian Codename or Suite.
  • component - The Debian Component.
  • architecture - The Debian Architecture.
  • packages - The list of Debian packages retrieved from the specified project and distribution.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID or URL-encoded path is correct to avoid 404 errors.
  • Verify that the 'distribution', 'component', and 'architecture' parameters are correctly specified as they are required for the API endpoint.
  • If authentication is enabled, ensure the GitLab API key credential is valid and has sufficient permissions to access the project packages.
  • Check the base URL if using a self-hosted GitLab instance to ensure it is correct.

Links

Discussion