GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to retrieve specific NuGet package details from a project. It is useful for developers or DevOps engineers who need to automate the retrieval of package metadata or verify package versions within GitLab projects. For example, it can be used to fetch the version details of a NuGet package in a CI/CD pipeline to ensure the correct package version is deployed.

Use Case Examples

  1. Retrieve NuGet package details for a specific project to verify package version before deployment.
  2. Automate fetching package metadata for auditing or reporting purposes within GitLab projects.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication when making the API request.
Authentication Specifies the authentication method to use, typically a GitLab API key.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to GET.
Parameter Schema Defines the required parameters for the API call, including project ID, package name, and package version.
Request Path The API endpoint path with placeholders for project ID, package name, and package version.
Query Parameters Collection of query parameters including package_name and package_version to specify the NuGet package details.
Path Parameters Collection of path parameters including project_id to specify the GitLab project.

Output

JSON

  • id - The unique identifier of the NuGet package.
  • name - The name of the NuGet package.
  • version - The version of the NuGet package.
  • project_id - The ID of the project to which the package belongs.
  • created_at - Timestamp when the package was created.
  • updated_at - Timestamp when the package was last updated.
  • metadata - Additional metadata related to the NuGet package.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project_id, package_name, and package_version parameters are correctly specified and URL-encoded if necessary.
  • Verify that the GitLab API key has sufficient permissions to access the project and its packages.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages include 404 Not Found if the package or project does not exist, and 401 Unauthorized if authentication fails. Verify credentials and permissions.

Links

Discussion