GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation resets the authentication token of a specific GitLab runner identified by its ID. It is useful in scenarios where the runner's authentication token needs to be refreshed or invalidated for security reasons or troubleshooting. For example, if a runner's token is compromised or needs to be rotated, this operation can be used to generate a new token.

Use Case Examples

  1. Resetting the authentication token of a GitLab runner with ID 123 to ensure secure communication.
  2. Refreshing the runner token after a security breach or token expiration.

Properties

Name Meaning
Skip Authentication Determines whether to skip the authentication process 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, defaulting to GET but can be POST, PUT, DELETE, HEAD, or PATCH.
Path Parameters The path parameters for the API request, specifically the runner ID to reset the authentication token for.

Output

JSON

  • id - The ID of the runner whose authentication token was reset.
  • token - The new authentication token generated for the runner.
  • created_at - Timestamp when the new token was created.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the runner ID provided in the path parameters is valid and exists in the GitLab instance.
  • Verify that the API authentication token has sufficient permissions to reset runner tokens.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • Common error messages include 404 Not Found if the runner ID does not exist, and 401 Unauthorized if authentication fails. Resolving these involves verifying the runner ID and API credentials respectively.

Links

Discussion