GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node operation deletes a specific Conan package from the GitLab package registry using the GitLab API. It is useful for managing and cleaning up package versions in a CI/CD pipeline or package management workflow. For example, it can be used to remove outdated or deprecated Conan packages from a project repository.

Use Case Examples

  1. Deleting a specific version of a Conan package from GitLab to free up storage and maintain package hygiene.
  2. Automating package cleanup in a DevOps pipeline by removing packages that are no longer needed or have been superseded.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip authentication when making the API request.
Authentication The authentication method used for the API request, typically a GitLab API key.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method used for the request, default is DELETE.
Path Parameters Parameters required in the API path to identify the specific Conan package to delete.

Output

JSON

  • success - Indicates whether the package deletion was successful.
  • statusCode - HTTP status code returned by the API.
  • message - Additional message or error details from the API response.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the provided package name, version, username, and channel are correct and exist in the GitLab package registry.
  • Verify that the API key used has sufficient permissions to delete packages in the target GitLab project or group.
  • Check the base URL to ensure it points to the correct GitLab instance if using a self-hosted GitLab server.
  • Common error messages include 404 Not Found if the package does not exist, and 403 Forbidden if the API key lacks delete permissions.

Links

Discussion