GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation deletes a specific Conan package from GitLab's package registry using the GitLab API. It is useful for managing and cleaning up package versions in a GitLab project, especially when you want to remove outdated or unwanted Conan packages programmatically.

Use Case Examples

  1. Deleting a specific version of a Conan package identified by its name, version, username, and channel in a GitLab project.
  2. Automating cleanup of old or deprecated Conan packages in a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API authentication. This property is hidden if Skip Authentication is true.
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 but can be set to DELETE for this operation.
Path Parameters Collection of path parameters required to identify the Conan package to delete, including package_name, package_version, package_username, and package_channel.

Output

JSON

  • response - The response from the GitLab API after attempting to delete the specified Conan package.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure that the package_name, package_version, package_username, and package_channel parameters are correctly specified and match the package to be deleted.
  • Verify that the authentication credentials are valid and have sufficient permissions to delete packages in the GitLab project.
  • Check the baseUrl to ensure it points to the correct GitLab instance.
  • If skipping authentication, ensure the GitLab instance allows unauthenticated DELETE requests, which is uncommon.
  • Common error messages may include 404 Not Found if the package does not exist, or 403 Forbidden if the user lacks permissions.

Links

Discussion