Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea server via its API, specifically allowing users to delete a repository variable. Repository variables in Gitea are key-value pairs associated with a repository, often used for configuration or automation purposes. Deleting a repository variable is useful when you want to remove sensitive data, outdated configuration, or clean up environment settings tied to a repository.

A practical example: If you have a CI/CD pipeline that uses repository variables for deployment credentials and you want to revoke access by removing those variables, this node operation will help automate that process.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository from which the variable should be deleted.
Variablename The exact name of the repository variable to delete.

Output

The node outputs JSON data representing the response from the Gitea API after attempting to delete the specified repository variable. Typically, for a delete operation, the output might be an empty object or a status confirmation indicating success or failure.

No binary data output is expected from this operation.

Dependencies

  • Requires connection to a Gitea instance via its REST API.
  • Needs an API authentication token configured in the node’s credentials to authorize requests.
  • The base URL for the Gitea API must be set in the credentials (e.g., https://your-gitea-instance/api/v1).

Troubleshooting

  • Common issues:

    • Incorrect owner or repository name can cause "Not Found" errors.
    • Specifying a variable name that does not exist will likely result in an error or no action.
    • Authentication failures if the API token is missing or invalid.
    • Network connectivity issues to the Gitea server.
  • Error messages:

    • 404 Not Found: Check that the owner, repo, and variable name are correct.
    • 401 Unauthorized: Verify that the API token credential is properly configured and has sufficient permissions.
    • 500 Internal Server Error: Could indicate server-side problems; retry later or check server logs.

Links and References

Discussion