GitLab API

GitlabTool

Actions905

Overview

This node interacts with the GitLab API to update application plan limits via a PUT request to the /api/v4/application/plan_limits endpoint. It is useful for automating the management of plan limits in GitLab applications, such as adjusting resource quotas or usage limits programmatically.

Use Case Examples

  1. Automatically update GitLab application plan limits based on usage metrics.
  2. Integrate plan limit adjustments into a CI/CD pipeline to enforce resource constraints.

Properties

Name Meaning
Skip Authentication Determines whether to skip API 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 to which the API request is sent.
Method HTTP method used for the API request, default is PUT for this operation.
Parameter Schema Defines the schema for the parameters sent in the request body for the putApiV4ApplicationPlanLimits operation.
Request Body Schema Schema for the request body payload, expected to conform to putApiV4ApplicationPlanLimits definition.
Request Path The API endpoint path for updating application plan limits.

Output

JSON

  • response - The JSON response from the GitLab API after updating the application plan limits.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the GitLab API key credential is valid and has sufficient permissions to update plan limits.
  • Verify the baseUrl is correct and accessible from the environment where the node runs.
  • Check that the request body conforms to the expected schema for plan limits to avoid validation errors.

Links

Discussion