GitLab API

GitlabTool

Actions905

Overview

This node operation deletes a specific NuGet package version from a GitLab project using the GitLab API. It is useful for managing and cleaning up NuGet packages in a project's package registry, especially when a package version is no longer needed or should be removed for security or maintenance reasons. For example, a user can delete an outdated or vulnerable NuGet package version from their GitLab project to ensure only approved versions are available.

Use Case Examples

  1. Deleting a deprecated NuGet package version from a project to prevent its usage.
  2. Removing a mistakenly published package version to maintain package registry integrity.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the API request.
Authentication Type of authentication used for the API request, defaulting to GitLab API key.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is DELETE for this operation.
Parameter Schema Defines the required parameters for the API call including project ID, package name, and package version.
Request Body Schema Schema for the request body, not used in this delete operation.
Request Path API endpoint path template for deleting the NuGet package version.
Query Parameters Collection of query parameters including package_name and package_version to specify which NuGet package version to delete.
Path Parameters Collection of path parameters including the project ID to identify the project from which the package will be deleted.

Output

JSON

  • statusCode - HTTP status code of the delete operation response.
  • responseBody - Response body returned from the GitLab API after the delete request.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID, package name, and package version are correctly specified; incorrect values will cause the API to fail.
  • Authentication errors may occur if the GitLab API key is missing or invalid; verify credentials are correctly configured.
  • The package version might not exist or may have already been deleted, resulting in a 404 Not Found error from the API.

Links

Discussion