GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation allows updating the job token scope settings for a specific project in GitLab via the GitLab API. It is useful for managing project-level job token permissions programmatically, such as enabling or restricting job token access for CI/CD pipelines.

Use Case Examples

  1. Updating the job token scope of a project to restrict or allow certain job token permissions.
  2. Automating project configuration changes related to job token scopes in GitLab through workflows.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the API request.
Authentication The authentication method used for the API request, typically an API key credential for GitLab.
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 GET but PATCH is used for this operation.
Path Parameters Parameters included in the API request path, specifically the project ID to identify which project's job token scope to update.

Output

JSON

  • response - The JSON response from the GitLab API after updating the job token scope, containing details of the updated settings.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the project ID provided in the path parameters is valid and accessible with the provided authentication.
  • Verify that the authentication credentials are correct and have sufficient permissions to update project settings.
  • Check the base URL to confirm it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common errors include 401 Unauthorized (authentication failure), 404 Not Found (invalid project ID), and 400 Bad Request (invalid request body).

Links

Discussion