GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves a specific Debian package file from a GitLab project's Debian package repository using the SHA256 hash of the file. It is useful for users who want to access or verify a particular Debian package binary by its hash within a GitLab project. For example, a developer or system administrator can use this to fetch a verified package binary for deployment or auditing purposes.

Use Case Examples

  1. Fetch a Debian package binary from a GitLab project by specifying the project ID, distribution codename, component, architecture, and the SHA256 hash of the file.
  2. Verify the integrity of a Debian package by retrieving it via its SHA256 hash from the GitLab package registry.

Properties

Name Meaning
Skip Authentication Option to skip authentication when making 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 project ID, distribution, component, architecture, and file SHA256 hash.
Request Body Schema Schema for the request body, not used in this GET operation.
Request Path The API endpoint path template for retrieving the Debian package file by SHA256 hash.
Query Parameters Collection of query parameters, specifically the Debian distribution codename or suite.
Path Parameters Collection of path parameters including project ID, Debian component, architecture, and file SHA256 hash.

Output

JSON

  • response - The JSON response containing the Debian package file data retrieved from the GitLab API.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the project ID and other path parameters are correctly specified and URL-encoded if necessary.
  • Verify that the SHA256 hash provided matches an existing file in the Debian package repository of the project.
  • Check that the authentication token has sufficient permissions to access the project's package registry.
  • If skipping authentication, ensure the GitLab instance allows unauthenticated access to the package registry.

Links

Discussion