GiteaInstall

Overview

This node interacts with a Gitea server via its API to update a secret in a specific repository. It is useful when you need to programmatically change or rotate secrets stored in a repository, such as API keys, tokens, or other sensitive data used by workflows or CI/CD pipelines.

Practical examples include:

• Automatically updating deployment keys or tokens after they expire.
• Rotating secrets on a schedule to improve security.
• Synchronizing secrets across multiple repositories or environments.

Properties

Output

The node outputs JSON data representing the response from the Gitea API after attempting to update the secret. This typically includes confirmation details about the updated secret or error information if the update failed.

No binary data output is involved.

Dependencies

• Requires an active connection to a Gitea instance with API access.
• Needs an API authentication token credential configured in n8n to authorize requests.
• The base URL of the Gitea server must be provided in the credentials configuration.

Troubleshooting

• Common issues:

  • Incorrect owner or repository names will cause the API call to fail.
  • Providing a secret name that does not exist may result in an error or no update.
  • Insufficient permissions or invalid API token will lead to authorization errors.
  • Malformed or empty data for the secret can cause the update to be rejected.

• Error messages and resolutions:

  • 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
  • 404 Not Found: Verify the owner, repository, and secret name are correct.
  • 400 Bad Request: Ensure the data property contains valid content and is properly formatted.

Links and References

• Gitea API Documentation
• Gitea Secrets Management (general concept, if available)