GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation updates the GitGuardian integration settings for a specific GitLab group by sending a PUT request to the GitLab API endpoint `/api/v4/groups/{id}/integrations/git-guardian`. It is useful for automating the configuration of security integrations within GitLab groups, such as enabling or modifying GitGuardian scanning features for code repositories.

Use Case Examples

  1. Automatically update GitGuardian integration settings for a GitLab group when a new project is created.
  2. Manage security integrations across multiple GitLab groups programmatically.

Properties

Name Meaning
Skip Authentication If set to true, the node will skip using authentication for the API request.
Authentication The authentication method used for the API request, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent, defaulting to https://gitlab.com.
Method The HTTP method used for the API request, defaulting to PUT for this operation.
Path Parameters Parameters included in the API request path, specifically the group ID to identify which group's GitGuardian integration to update.

Output

JSON

  • response - The JSON response from the GitLab API after updating the GitGuardian integration settings, containing the updated integration details.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the group ID provided in the path parameters is valid and the authenticated user has permission to update integrations for that group.
  • Verify that the GitLab API base URL is correct and accessible.
  • Check that the authentication credentials are valid and have the necessary scopes to perform integration updates.
  • Common error messages may include 401 Unauthorized (invalid or missing credentials), 404 Not Found (invalid group ID), or 400 Bad Request (invalid request body). Resolving these involves correcting credentials, verifying group existence, and ensuring request body schema compliance.

Links

Discussion