GitLab API

GitlabTool
Join our community

Actions1000

Overview

This node operation deletes a specific GPG key associated with a user in GitLab. It is useful for managing user security keys by removing outdated or compromised GPG keys. For example, an administrator can use this operation to revoke a user's GPG key access via the GitLab API.

Use Case Examples

  1. Deleting a user's GPG key by specifying the user ID and the GPG key ID.
  2. Automating the removal of GPG keys for users who no longer require them.

Properties

Name Meaning
Skip Authentication Determines whether to skip the authentication process for the API 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 The HTTP method used for the API request, defaulting to GET but can be set to DELETE for this operation.
Path Parameters Parameters included in the API request path to specify the user ID and the GPG key ID to delete.

Output

JSON

  • success - Indicates whether the GPG key deletion was successful.
  • statusCode - HTTP status code returned from the API request.

Dependencies

  • GitLab API key credential

Troubleshooting

  • Ensure the user ID and GPG key ID are correct and exist in the GitLab instance.
  • Verify that the API key used has sufficient permissions to delete user GPG keys.
  • Check the base URL to confirm it points to the correct GitLab instance.
  • Common error messages include 404 Not Found if the user or key does not exist, and 403 Forbidden if the API key lacks permissions.

Links

Discussion