GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation deletes the dependency proxy cache for a specific group in GitLab. It is useful for clearing cached dependencies to ensure that the latest versions are used or to free up storage space. A practical example is when a user wants to clear the cache for a group to resolve issues related to outdated or corrupted cached dependencies.

Use Case Examples

  1. Deleting the dependency proxy cache for a group identified by its ID or URL-encoded path.
  2. Automating cache clearing as part of a CI/CD pipeline to maintain up-to-date dependencies.

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 authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method The HTTP method to use for the request, defaulting to GET but can be set to DELETE for this operation.
Path Parameters The path parameters for the API request, specifically the 'id' which is the ID or URL-encoded path of the group owned by the authenticated user.

Output

JSON

  • statusCode - The HTTP status code returned by the API after attempting to delete the cache.
  • responseBody - The body of the response returned by the API, which may contain details about the deletion operation or errors.

Dependencies

  • GitLab API authentication token

Troubleshooting

  • Ensure the 'id' path parameter is correctly set to the group's ID or URL-encoded path; otherwise, the API call will fail.
  • If authentication is skipped, the request may be unauthorized unless the GitLab instance allows anonymous access for this operation.
  • Check that the baseUrl is correctly set to the GitLab instance URL if using a self-hosted GitLab server.
  • Common error messages include 401 Unauthorized (authentication issues), 404 Not Found (invalid group ID), and 403 Forbidden (insufficient permissions).

Links

Discussion