GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation allows adding groups to the job token scope allowlist for a specific project in GitLab. It is useful for managing which groups are permitted to use job tokens within a project, enhancing security and access control. For example, a DevOps engineer can use this node to programmatically update the allowlist of groups that can access CI/CD job tokens for a project.

Use Case Examples

  1. Add a group to the job token scope allowlist for project ID 123 to control CI/CD job token access.
  2. Automate updating the allowlist when new groups are created or permissions change.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, default is GitLab API key.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET.
Path Parameters Parameters to be included in the request path, specifically the project ID for this operation.

Output

JSON

  • response - The JSON response from the GitLab API after adding groups to the job token scope allowlist.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the project ID provided in path parameters is valid and accessible with the authenticated user.
  • Verify that the GitLab API key has sufficient permissions to modify job token scope allowlists.
  • Check the baseUrl is correctly set to the GitLab instance URL if using a self-hosted GitLab.
  • Common errors include 401 Unauthorized (invalid or missing API key), 404 Not Found (invalid project ID), and 403 Forbidden (insufficient permissions).

Links

Discussion