GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation allows deleting a GitLab runner manager by making an HTTP DELETE request to the GitLab API endpoint `/api/v4/runners/managers`. It requires the runner's authentication token and system identifier as query parameters. This operation is useful for managing GitLab runners programmatically, such as removing runner managers that are no longer needed or are being replaced.

Use Case Examples

  1. Deleting a specific GitLab runner manager by providing its token and system ID to automate runner management in CI/CD pipelines.
  2. Automating cleanup of runner managers in GitLab projects to maintain security and resource efficiency.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request (boolean). Defaults to false.
baseUrl The base URL of the GitLab instance. Defaults to https://gitlab.com.
Method HTTP method to use for the request. Defaults to DELETE for this operation.
Query Parameters Collection of query parameters required for the request, including the runner's authentication token and system identifier.

Output

JSON

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

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the token and system_id query parameters are correctly provided and valid; missing or incorrect values will cause the API request to fail.
  • If authentication is skipped, ensure the GitLab instance allows unauthenticated requests or the operation will fail.
  • Check the baseUrl if using a self-hosted GitLab instance to ensure the correct API endpoint is targeted.
  • Common error messages include 401 Unauthorized (invalid or missing authentication), 404 Not Found (runner manager not found), and 400 Bad Request (missing required parameters).

Links

Discussion