GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation deletes a specific Conan package version from a GitLab project using the GitLab API. It is useful for managing and cleaning up package repositories by removing outdated or unwanted Conan packages. For example, a user can delete a particular version of a Conan package associated with a project to free up storage or remove deprecated versions.

Use Case Examples

  1. Deleting a specific version of a Conan package from a GitLab project to maintain package repository hygiene.
  2. Automating cleanup of old or unused Conan packages in a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, default is GET but DELETE is used for this operation.
Parameter Schema Defines the required path parameters for the API request, including project ID, package name, version, username, and channel.
Path Parameters Collection of path parameters specifying the project ID, package name, package version, package username, and package channel to identify the Conan package to delete.

Output

JSON

  • statusCode - HTTP status code of the API response indicating success or failure of the delete operation.
  • body - Response body from the API, typically empty or containing confirmation of deletion.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure all required path parameters (id, package_name, package_version, package_username, package_channel) are correctly provided; missing or incorrect parameters will cause the API call to fail.
  • Authentication errors may occur if the API key credential is missing, invalid, or lacks sufficient permissions to delete packages.
  • Network or base URL misconfiguration can lead to connection failures; verify the baseUrl is correct and accessible.
  • API rate limits or permission restrictions on the GitLab instance may cause errors; check user permissions and API usage limits.

Links

Discussion