GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation deletes a specific release asset link from a GitLab project release. It is useful for managing release assets by removing outdated or incorrect links associated with a release tag. For example, if a release asset link is no longer valid or needs to be replaced, this operation can be used to delete it programmatically.

Use Case Examples

  1. Deleting a release asset link by specifying the project ID, release tag name, and the link ID to remove an obsolete asset link from a release.
  2. Automating cleanup of release assets in CI/CD pipelines by removing links that are no longer needed after deployment.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, default is 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 GET.
Parameter Schema Defines the required path parameters for the delete operation: project ID, release tag name, and link ID.
Request Body Schema Schema for the request body, null for this delete operation.
Request Path API endpoint path for deleting the release asset link.
Path Parameters Collection of path parameters including project ID, release tag name, and link ID to identify the specific release asset link to delete.

Output

JSON

  • success - Indicates whether the deletion was successful.
  • statusCode - HTTP status code returned by the API.
  • message - Additional message or details about the deletion result.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID, tag name, and link ID are correct and exist in the GitLab project.
  • Verify that the API key used has sufficient permissions to delete release asset links.
  • Check the base URL if using a self-hosted GitLab instance to ensure it is correct.
  • Common error messages include 404 Not Found if the resource does not exist, and 403 Forbidden if authentication or permissions are insufficient.

Links

Discussion