Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance to retrieve a list of repository variables. Specifically, the "Get Repo Variables List" operation fetches environment or configuration variables defined for a given repository. This is useful in scenarios where you want to programmatically access repository-level variables for automation, auditing, or integration purposes.

Practical examples include:

  • Automating deployment pipelines by fetching repo variables dynamically.
  • Auditing or backing up repository configuration settings.
  • Integrating repository variables into other workflows or systems.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository from which to retrieve variables.
Page (Optional) The page number of results to return, starting at 1. Used for pagination.
Limit (Optional) The number of results per page to return. Controls page size for pagination.

Output

The node outputs JSON data containing an array of repository variables. Each variable typically includes details such as its name, value (or masked value), and possibly metadata like creation date or visibility. The exact structure depends on the Gitea API response but generally provides all relevant information about each repository variable.

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 credentials to authorize requests.
  • The base URL of the Gitea server must be set in the credentials.

Troubleshooting

  • Common issues:

    • Authentication failures due to invalid or missing API tokens.
    • Incorrect owner or repository names causing "not found" errors.
    • Pagination parameters out of range or zero values leading to empty responses.
  • Error messages:

    • 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
    • 404 Not Found: Verify the owner and repository names are correct and accessible.
    • 400 Bad Request: Ensure pagination parameters (page, limit) are positive integers.

Resolving these usually involves verifying credentials, input parameters, and network connectivity to the Gitea server.

Links and References

Discussion