GiteaInstall

Overview

This node interacts with a Gitea instance via its API, specifically allowing users to delete a secret from a repository. It is useful in scenarios where repository secrets need to be managed programmatically, such as removing outdated or compromised secrets from a repository's settings.

For example, if you have automated workflows that manage deployment keys or environment variables stored as secrets in your repositories, this node can help you remove those secrets when they are no longer needed or must be rotated.

Properties

Output

The node outputs JSON data representing the result of the delete operation. Typically, for a delete action, the output might be an empty object or a confirmation message indicating success. There is no indication that binary data is involved in this operation.

Dependencies

• Requires access to a Gitea instance with API enabled.
• Needs an API authentication token configured in the node credentials to authorize requests.
• The base URL for the Gitea API must be provided in the credentials configuration.

Troubleshooting

• Common issues:

  • Incorrect owner, repository, or secret name will cause the deletion to fail.
  • Insufficient permissions or invalid API token may result in authorization errors.
  • Network connectivity problems to the Gitea server can prevent the request from completing.

• Error messages and resolutions:

  • 404 Not Found: Verify that the owner, repository, and secret name are correct and exist.
  • 401 Unauthorized or 403 Forbidden: Check that the API token has sufficient permissions to delete repository secrets.
  • Network errors: Ensure the Gitea server URL is reachable and correctly set in credentials.

Links and References

• Gitea API Documentation (for repository secrets management)
• n8n Documentation (general guidance on using API nodes and credentials)