GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation updates an existing cluster in the GitLab Admin API by sending a PUT request to the endpoint `/api/v4/admin/clusters/{cluster_id}`. It is useful for administrators who need to modify cluster configurations programmatically, such as changing cluster details or settings in an automated workflow.

Use Case Examples

  1. Updating cluster details in GitLab Admin via n8n automation.
  2. Automating cluster configuration changes based on external triggers.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the request.
Authentication Specifies the authentication method to use, 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 PUT for this operation.
Path Parameters Parameters to be included in the request path, specifically the cluster ID to identify which cluster to update.

Output

JSON

  • response - The JSON response from the GitLab API after updating the cluster, containing updated cluster details or status.

Dependencies

  • Requires GitLab API key credential for authentication unless skipping authentication is enabled.

Troubleshooting

  • Ensure the cluster_id path parameter is provided and valid; missing or incorrect cluster_id will cause request failure.
  • Authentication errors may occur if the GitLab API key is invalid or missing; verify credentials are correctly configured.
  • HTTP errors such as 404 (Not Found) or 403 (Forbidden) may indicate insufficient permissions or non-existent cluster ID.

Links

Discussion