GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation revokes a specific GPG key for the authenticated user in GitLab. It is useful for managing user security by invalidating GPG keys that are no longer needed or compromised. For example, a user can revoke a GPG key by providing its ID, ensuring it can no longer be used for signing commits or tags.

Use Case Examples

  1. Revoking a compromised GPG key to prevent unauthorized use.
  2. Removing an old GPG key that is no longer in use.

Properties

Name Meaning
Skip Authentication Whether to skip authentication for the request.
Authentication The authentication method used, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method The HTTP method used for the request, here it is POST for revoking the GPG key.
Path Parameters Parameters included in the request path, specifically the GPG key ID to revoke.

Output

JSON

  • statusCode - HTTP status code of the revoke operation response.
  • body - Response body from the GitLab API after revoking the GPG key, typically empty or confirmation message.

Dependencies

  • GitLab API with authentication credentials

Troubleshooting

  • Ensure the provided GPG key ID is valid and belongs to the authenticated user.
  • Check that the authentication credentials are correct and have sufficient permissions to revoke GPG keys.
  • Verify the base URL is correct for the GitLab instance being accessed.

Links

Discussion