GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation updates a specific asset link of a release in a GitLab project using the GitLab API. It is useful for managing release assets by modifying existing links associated with a release tag. For example, it can be used to update the URL or name of a release asset link in a CI/CD pipeline or release management workflow.

Use Case Examples

  1. Updating the URL of a release asset link to point to a new location.
  2. Changing the name or description of an asset link associated with a release tag.

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 or token.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, here it is PUT for updating resources.
Path Parameters Parameters required in the API request path to identify the project, release tag, and link ID to update.

Output

JSON

  • id - The ID of the updated asset link.
  • name - The name of the updated asset link.
  • url - The URL of the updated asset link.
  • link_type - The type of the link (e.g., other, image, etc.).
  • direct_asset_url - Direct URL to the asset if available.
  • filepath - File path of the asset if applicable.

Dependencies

  • GitLab API authentication token or API key

Troubleshooting

  • Ensure the project ID, release tag name, and link ID are correctly specified; incorrect values will cause the API request to fail.
  • Authentication errors may occur if the API token is missing, expired, or lacks sufficient permissions; verify the token and its scopes.
  • The API endpoint requires the PUT method; using other methods will result in errors.
  • Network or base URL misconfiguration can cause connection failures; verify the baseUrl property.

Links

Discussion