GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation allows revoking a GPG key for a user in GitLab by making a POST request to the GitLab API endpoint `/api/v4/user/gpg_keys/{key_id}/revoke`. It is useful for managing user security by invalidating GPG keys that are no longer needed or compromised.

Use Case Examples

  1. Revoking a specific GPG key by providing its key ID to enhance user account security.
  2. Automating the process of GPG key revocation in GitLab user management workflows.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, default is false.
Authentication Type of authentication used, default is GitLab API key. Hidden if Skip Authentication is true.
baseUrl Base URL for the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET. Options include GET, POST, PUT, DELETE, HEAD, PATCH.
Path Parameters Collection of path parameters required for the request, specifically the key_id of the GPG key to revoke.

Output

JSON

  • statusCode - HTTP response status code indicating the result of the revoke operation.
  • body - Response body from the GitLab API after attempting to revoke the GPG key, typically contains success or error details.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the provided key_id is valid and exists in the user's GPG keys to avoid 404 errors.
  • Check that the authentication credentials are correctly configured unless Skip Authentication is enabled.
  • Verify the baseUrl is correct for the GitLab instance being accessed.
  • Common error messages may include authentication failures, invalid key_id, or permission denied errors. Resolving these involves checking API token permissions and input parameters.

Links

Discussion