GitLab API

GitlabTool

Actions905

Overview

This node operation retrieves a specific deploy token from a GitLab group using the GitLab API. It is useful for automating the management and retrieval of deploy tokens associated with groups in GitLab, which can be used for deployment automation and access control.

Use Case Examples

  1. Fetch details of a deploy token for a specific GitLab group to verify its permissions or expiration.
  2. Automate the retrieval of deploy tokens for integration with CI/CD pipelines.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated API calls.
Authentication Select the authentication method, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Path Parameters Parameters to specify the group ID and deploy token ID for the API request.

Output

JSON

  • id - The unique identifier of the deploy token.
  • name - The name of the deploy token.
  • username - The username associated with the deploy token.
  • scopes - The scopes or permissions granted to the deploy token.
  • created_at - The creation timestamp of the deploy token.
  • expires_at - The expiration date of the deploy token, if set.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the provided group ID and deploy token ID are correct and accessible by the authenticated user.
  • Check that the GitLab API key credential has sufficient permissions to access group deploy tokens.
  • If skipping authentication, verify that the GitLab instance allows unauthenticated access to deploy token information, which is uncommon.
  • Common error messages include 404 Not Found if the group or token does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion