GiteaInstall

Overview

This node operation allows you to delete a deploy key from a specific repository in Gitea, a self-hosted Git service. Deploy keys are SSH keys that grant read or write access to a repository without using a user’s personal credentials. This operation is useful for managing repository access securely by removing keys that are no longer needed or have been compromised.

Common scenarios include:

• Revoking access for automated systems or CI/CD pipelines that no longer require repository access.
• Cleaning up old or unused deploy keys to maintain repository security.
• Managing repository permissions programmatically as part of infrastructure automation.

Example: You have a repository named "my-project" owned by "alice" and want to remove a deploy key with ID 12345 that was previously added for deployment purposes.

Properties

Output

The output of this operation typically contains the response from the API confirming the deletion of the deploy key. Since this is a delete operation, the JSON output may be empty or contain status information indicating success. No binary data is expected.

Dependencies

• Requires an API key credential for authenticating with the Gitea instance.
• The node must be configured with the base URL of the Gitea server.
• Network access to the Gitea API endpoint /api/v1 is necessary.

Troubleshooting

• Invalid Owner or Repo: If the owner or repository name is incorrect, the API will return an error indicating the repository was not found. Verify the spelling and case sensitivity.
• Invalid Key ID: Providing a non-existent deploy key ID will result in an error. Confirm the key ID before attempting deletion.
• Authentication Errors: Ensure the API key credential has sufficient permissions to manage deploy keys on the target repository.
• Network Issues: Check connectivity to the Gitea server and ensure the base URL is correctly set in the node credentials.

Links and References

• Gitea API Documentation - Repository Deploy Keys
• Managing Deploy Keys in Gitea