Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with the Gitea API to list secrets associated with actions in a specified organization. It is useful for users who want to programmatically retrieve and manage action secrets within their Gitea organizations, such as for automation or auditing purposes.

A practical example would be fetching all action secrets for an organization to verify which secrets are currently configured or to synchronize secrets across multiple environments.

Properties

Name Meaning
Org The name of the organization whose action secrets you want to list.
Page The page number of results to return (1-based). Useful for paginating through large sets.
Limit The number of results to return per page (page size).

Output

The node outputs JSON data representing the list of action secrets for the specified organization. Each item in the output typically contains details about an individual secret, such as its name and metadata related to its usage in actions.

No binary data output is involved.

Dependencies

  • Requires an API key credential to authenticate with the Gitea instance.
  • Needs the base URL of the Gitea server configured in the credentials.
  • Relies on the Gitea REST API endpoint /api/v1 for organization action secrets.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect organization name may result in empty results or errors.
    • Pagination parameters (page and limit) set incorrectly might lead to unexpected result counts or no data.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API tokens; ensure the token has sufficient permissions.
    • "Not Found" errors suggest the organization does not exist or the user lacks access rights.
    • Rate limiting errors from the API require waiting or adjusting request frequency.

Links and References

Discussion