GitLab API

GitlabTool

Actions1000

Overview

This node operation retrieves the InRelease file for a specific Debian distribution within a project's Debian packages on GitLab. It is useful for users who want to access metadata about Debian package distributions in a GitLab project, such as verifying package authenticity and integrity.

Use Case Examples

  1. A DevOps engineer uses this node to fetch the InRelease file for a Debian distribution named 'my-distro' in a project with a specific ID to automate package verification in a CI/CD pipeline.
  2. A developer queries the InRelease file to check the distribution metadata before deploying Debian packages from a GitLab project.

Properties

Name Meaning
Skip Authentication Option to skip API authentication, useful for public projects or testing without credentials.
Authentication Type of authentication used for the API request, defaulting to GitLab API key authentication.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method used 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 ID or URL-encoded path of the project.

Output

JSON

  • id - The ID or URL-encoded path of the project.
  • distribution - The Debian Codename or Suite specified in the query parameter.
  • InRelease - The InRelease file content retrieved for the specified Debian distribution in the project.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the project ID ('id') and distribution name ('distribution') are correctly specified; incorrect values will result in API errors or empty responses.
  • If authentication is enabled, verify that the GitLab API key credential is valid and has sufficient permissions to access the project's Debian packages.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct and accessible.
  • Common error messages include 404 Not Found if the project or distribution does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion