GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to reset the registration token for GitLab runners. It is useful in scenarios where you need to invalidate the current registration token and generate a new one for security or operational reasons. For example, if a runner's token is compromised or you want to rotate tokens regularly, this node can automate the reset process.

Use Case Examples

  1. Resetting the registration token for GitLab runners to enhance security.
  2. Automating token rotation for GitLab runners in CI/CD pipelines.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, defaulting to POST for this operation.
Parameter Schema Schema for parameters used in the API request, hidden and not user-configurable.
Request Body Schema Schema for the request body, hidden and not user-configurable.
Request Path The API endpoint path for resetting the registration token, fixed to /api/v4/runners/reset_registration_token.

Output

JSON

  • response - The JSON response from the GitLab API containing the new registration token and related information.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the GitLab API key credential is valid and has sufficient permissions to reset runner registration tokens.
  • Verify the baseUrl is correctly set to the GitLab instance URL.
  • Check network connectivity to the GitLab server.
  • Common error messages include authentication failures (401 Unauthorized) and permission errors (403 Forbidden), which can be resolved by verifying credentials and permissions.

Links

Discussion