GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation retrieves Debian package information from a specified GitLab group using the GitLab API. It is useful for automating the fetching of Debian package metadata for specific distributions, components, and architectures within a GitLab group repository. For example, it can be used to programmatically access package lists for deployment or auditing purposes.

Use Case Examples

  1. Fetch Debian packages for a group with ID '123' for the 'my-distro' distribution, 'main' component, and 'binary-amd64' architecture.
  2. Automate retrieval of Debian package metadata from a GitLab group to integrate with CI/CD pipelines.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making the API request.
Authentication Type of authentication used for the API request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance to which the API request is sent.
Method HTTP method used for the API request (GET, POST, PUT, DELETE, HEAD, PATCH).
Query Parameters Query parameters for the API request, specifically the Debian distribution codename or suite.
Path Parameters Path parameters for the API request including group ID or path, Debian component, and architecture.

Output

JSON

  • id - The group ID or full group path used in the request.
  • distribution - The Debian Codename or Suite specified in the query parameters.
  • component - The Debian Component specified in the path parameters.
  • architecture - The Debian Architecture specified in the path parameters.
  • packages - The list of Debian packages retrieved from the GitLab group for the specified distribution, component, and architecture.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the group ID or full group path is correct and accessible with the provided authentication.
  • Verify that the Debian distribution, component, and architecture parameters are correctly specified and exist in the GitLab group repository.
  • Check that the GitLab API key credential is valid and has sufficient permissions to access the group packages.
  • Common error messages may include authentication failures, 404 not found if the group or packages do not exist, and 400 bad request if parameters are missing or invalid.

Links

Discussion