GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation allows users to delete a GitLab runner by making an HTTP DELETE request to the GitLab API endpoint `/api/v4/runners`. It is useful for managing CI/CD runners in GitLab, particularly when you need to remove a runner using its authentication token. For example, a DevOps engineer can automate the cleanup of unused or compromised runners in their GitLab instance.

Use Case Examples

  1. Automate deletion of a GitLab runner by providing its token to the node.
  2. Integrate runner management in a CI/CD pipeline to remove runners dynamically.

Properties

Name Meaning
Skip Authentication Determines whether to skip the authentication step for the API request.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, default is DELETE for this operation.
Query Parameters Collection of query parameters for the request, specifically the runner's authentication token required to identify the runner to delete.

Output

JSON

  • statusCode - HTTP status code returned by the GitLab API indicating the result of the delete operation.
  • responseBody - The body of the response from the GitLab API, typically empty or containing confirmation of deletion.

Dependencies

  • GitLab API authentication token or credential

Troubleshooting

  • Ensure the runner token provided in the query parameters is correct and valid; an invalid token will cause the deletion to fail.
  • Check that the base URL is correctly set to the GitLab instance you intend to manage; incorrect URLs will lead to connection errors.
  • If skipping authentication, ensure the GitLab instance allows unauthenticated requests for this operation, which is uncommon and may cause authorization errors.

Links

Discussion