GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation allows updating the Harbor integration settings for a specific GitLab group by sending a PUT request to the GitLab API endpoint `/api/v4/groups/{id}/integrations/harbor`. It is useful for managing and configuring Harbor container registry integration within GitLab groups programmatically.

Use Case Examples

  1. Updating Harbor integration settings for a GitLab group by specifying the group ID and providing the necessary configuration in the request body.
  2. Automating the management of container registry integrations across multiple GitLab groups in a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, defaulting to GitLab API key authentication.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the request, default is GET but for this operation it is PUT.
Path Parameters The path parameters for the API request, specifically the group ID (`id`) to identify which group's Harbor integration to update.

Output

JSON

  • id - The ID of the GitLab group for which the Harbor integration was updated.
  • integrationStatus - The status or result of the Harbor integration update operation.
  • updatedFields - Details of the fields that were updated in the Harbor integration settings.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the group ID (`id`) path parameter is correctly provided and corresponds to an existing GitLab group.
  • Verify that the request body contains valid and complete Harbor integration settings as required by the GitLab API.
  • Check that the base URL is correctly set to the GitLab instance URL if using a self-hosted GitLab server.
  • If skipping authentication, ensure the API endpoint allows unauthenticated requests, otherwise authentication errors will occur.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid group ID or endpoint), and 400 Bad Request (invalid request body). Resolving these involves verifying credentials, parameters, and request payloads.

Discussion