GitLab API

GitlabTool
Join our community

Actions905

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 to maintain security. For example, if a deploy token is no longer in use or has been exposed, this operation can be used to revoke its access by deleting it from the group.

Use Case Examples

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

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, typically used for public or unauthenticated endpoints.
Authentication Specifies the authentication method to use, defaulting to GitLab API 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.

Output

JSON

  • statusCode - HTTP status code of the delete operation response.
  • body - Response body from the GitLab API after attempting to delete the deploy token, typically empty for successful delete.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the provided group ID and deploy token ID are correct and exist in the GitLab instance.
  • Verify that the API authentication token has sufficient permissions to delete deploy tokens in the specified group.
  • Check the base URL to confirm it points to the correct GitLab instance 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 authentication lacks necessary permissions.

Links

Discussion