GitLab API

GitlabTool

Actions1000

Overview

This node operation deletes a specific token associated with a cluster agent in a GitLab project. It is useful for managing and revoking access tokens for cluster agents, ensuring security and control over agent permissions. For example, if a token is compromised or no longer needed, this operation can be used to remove it.

Use Case Examples

  1. Deleting a compromised cluster agent token to prevent unauthorized access.
  2. Removing an expired or unused token from a cluster agent to maintain security hygiene.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, defaulting to 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 but DELETE is used for this operation.
Path Parameters Parameters required in the request path to identify the project, cluster agent, and token to delete.

Output

JSON

  • statusCode - HTTP status code of the delete operation response
  • responseBody - Response body returned from the GitLab API after deleting the token

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the provided project ID, agent ID, and token ID are correct and exist in the GitLab instance.
  • Verify that the API key used has sufficient permissions to delete cluster agent tokens.
  • Check network connectivity and the base URL configuration if requests fail.
  • Common error messages include 404 Not Found if the token or agent does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion