GitLab API

GitlabTool

Actions905

Overview

This node operation deletes a specific feature in GitLab by its name using the GitLab API. It is useful for automating the removal of feature flags or feature toggles in GitLab projects, which can help manage feature lifecycle and deployment processes.

Use Case Examples

  1. Deleting a feature flag named 'new-ui' to disable a new user interface feature in a GitLab project.
  2. Automating cleanup of deprecated features in a CI/CD pipeline.

Properties

Name Meaning
Skip Authentication Determines whether to skip API authentication for the request.
Authentication Specifies the authentication method to use, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method HTTP method used for the request, here it is DELETE to remove a feature.
Path Parameters Parameters included in the API request path, specifically the 'name' of the feature to delete.

Output

JSON

  • success - Indicates whether the feature deletion was successful.
  • statusCode - HTTP status code returned by the API after the delete request.
  • message - Additional message or information about the deletion result.

Dependencies

  • GitLab API with an API key credential for authentication

Troubleshooting

  • Ensure the 'name' path parameter is correctly set to the feature name intended for deletion; otherwise, the API will return an error.
  • If authentication is skipped or credentials are invalid, the API will reject the request with an authentication error.
  • Check the baseUrl to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages include '404 Not Found' if the feature name does not exist, or '401 Unauthorized' if authentication fails.

Links

Discussion