GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves the InRelease file for a specific Debian distribution within a GitLab group. It is useful for users who want to access Debian package metadata for a given distribution codename or suite in a GitLab group's package registry. For example, it can be used to automate fetching package release information for Debian-based software deployment or CI/CD pipelines.

Use Case Examples

  1. Fetch the InRelease file for the 'buster' distribution in a GitLab group with ID '12345' to verify package integrity and metadata.
  2. Retrieve Debian package distribution information for a custom distribution named 'my-distro' in a GitLab group path.

Properties

Name Meaning
Skip Authentication Whether to skip authentication when making the API request.
Authentication The authentication method used for the API request, typically a GitLab API key.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request (GET, POST, PUT, DELETE, HEAD, PATCH).
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, specifically the 'id' parameter representing the group ID or full group path.

Output

JSON

  • id - The group ID or full group path used in the request path.
  • distribution - The Debian Codename or Suite specified as a query parameter.
  • InRelease - The content of the InRelease file for the specified Debian distribution retrieved from the GitLab API.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the 'id' path parameter is correctly set to a valid GitLab group ID or full group path; otherwise, the API request will fail with a 404 or authentication error.
  • Verify that the 'distribution' query parameter is correctly specified as a valid Debian Codename or Suite; an incorrect value may result in no data or an error response.
  • If authentication is enabled, ensure the GitLab API key credential is valid and has sufficient permissions to access the group's Debian packages.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure the API endpoint is reachable.

Discussion