GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation interacts with the GitLab API to retrieve the InRelease file for a specific Debian distribution within a group's Debian package repository. It is useful for automating the retrieval of Debian package metadata for a given distribution codename or suite in a GitLab group. For example, it can be used in CI/CD pipelines or automation workflows to verify or process Debian package distributions hosted on GitLab.

Use Case Examples

  1. Retrieve the InRelease file for the 'buster' distribution in a GitLab group with ID '12345'.
  2. Automate the fetching of Debian package metadata for a custom distribution in a GitLab group to integrate with deployment scripts.

Properties

Name Meaning
Skip Authentication Option to skip API authentication, useful for public or unauthenticated access scenarios.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method 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, 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 retrieved from the Debian distribution in the GitLab group.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the group ID or full group path ('id') is correctly specified and exists in GitLab.
  • Verify the 'distribution' query parameter matches a valid Debian Codename or Suite available in the group's Debian package repository.
  • If authentication is enabled, confirm that the GitLab API key credential is valid and has sufficient permissions to access the group's packages.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct and accessible.

Links

Discussion