GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation deletes a specific deploy token from a GitLab group. It is useful for managing access tokens that allow automated deployments or integrations, ensuring that tokens no longer needed or compromised can be removed securely. For example, a DevOps engineer might use this node to revoke a deploy token after a project is completed or when rotating credentials for security purposes.

Use Case Examples

  1. Deleting a deploy token from a GitLab group to revoke its access.
  2. Automating the cleanup of deploy tokens in CI/CD pipelines.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for testing or when authentication is handled externally.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but DELETE is used for this operation.
Path Parameters Parameters required in the URL path to identify the group and the deploy token to delete, specifically 'id' for the group and 'token_id' for the deploy token.

Output

JSON

  • success - Indicates whether the deploy token was successfully deleted
  • statusCode - HTTP status code returned by the GitLab API
  • message - Additional message or error details from the API response

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the provided group ID and deploy token ID are correct and that the authenticated user has permission to delete deploy tokens for the group.
  • If authentication is skipped, the request may fail due to lack of authorization.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages include 404 Not Found if the group or token does not exist, and 403 Forbidden if the user lacks permission.

Links

Discussion