GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation deletes a specific GPG key associated with the authenticated user in GitLab. It is useful for managing user security keys by removing outdated or compromised GPG keys from the user's GitLab account. For example, a user can automate the removal of a GPG key by specifying its key ID, ensuring their account only retains valid keys.

Use Case Examples

  1. Deleting a GPG key by providing its key ID to revoke its access.
  2. Automating cleanup of user GPG keys in GitLab for security maintenance.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used for the request, defaulting to GitLab API key.
baseUrl Base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method for the request, defaulting to DELETE for this operation.
Parameter Schema Schema defining the path parameter key_id which is the ID of the GPG key to delete.
Request Body Schema Schema for the request body, null for this operation as no body is needed.
Request Path API endpoint path with placeholder for key_id to specify which GPG key to delete.
Path Parameters Collection of path parameters including key_id which identifies the GPG key to delete.

Output

JSON

  • success - Indicates if the GPG key deletion was successful
  • statusCode - HTTP status code returned from the API request
  • responseBody - The body of the response from the API, typically empty for delete operations

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the key_id parameter is provided and is a valid integer representing an existing GPG key ID.
  • Authentication errors may occur if the GitLab API key is missing or invalid; verify credentials are correctly configured.
  • API endpoint errors may happen if the baseUrl is incorrect or the GitLab instance is unreachable.

Links

Discussion