GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves Debian package distribution information from a GitLab group using the GitLab API. It is useful for automating the management and retrieval of Debian package metadata within GitLab groups, especially when working with specific Debian distributions, components, architectures, and package files identified by SHA256 hashes. For example, it can be used to fetch package details for deployment or auditing purposes in CI/CD pipelines.

Use Case Examples

  1. Fetch Debian package distribution details for a specific group and distribution to verify package availability.
  2. Automate retrieval of package metadata for a given Debian architecture and component within a GitLab group.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, default is GET.
Parameter Schema Defines the required path and query parameters for the API call, including group ID, Debian distribution, component, architecture, and file SHA256 hash.
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, Debian component, architecture, and file SHA256 hash.

Output

JSON

  • id - The group ID or full group path.
  • distribution - The Debian Codename or Suite.
  • component - The Debian Component.
  • architecture - The Debian Architecture.
  • file_sha256 - The SHA256 hash of the Debian package file.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the group ID and full group path are correct to avoid 404 errors.
  • Verify that the Debian distribution, component, architecture, and file SHA256 hash parameters are accurate and exist in the GitLab group.
  • Check API authentication credentials if authentication is not skipped to prevent authorization errors.
  • Confirm the base URL is correct if using a self-hosted GitLab instance to avoid connection issues.

Links

Discussion