Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node interacts with a Gitea instance to list deploy keys associated with a specific repository. It is useful for users who want to programmatically retrieve SSH keys that have access to a repository, for example, to audit keys, manage access, or automate repository security checks.

Typical use cases include:

  • Fetching all deploy keys of a repository to verify authorized access.
  • Filtering keys by ID or fingerprint to find specific keys.
  • Paginating through large sets of keys when repositories have many deploy keys.

Properties

Name Meaning
Owner The username or organization name that owns the repository.
Repo The name of the repository from which to list deploy keys.
Key Id (Optional) Filter results to a specific key by its unique identifier.
Fingerprint (Optional) Filter results by the fingerprint of the deploy key.
Page (Optional) The page number of results to return, starting at 1. Used for pagination.
Limit (Optional) The maximum number of results to return per page.

Output

The node outputs JSON data representing the list of deploy keys retrieved from the specified repository. Each item in the output array typically includes details such as the key's ID, title, key content, fingerprint, and creation date.

If binary data were involved (e.g., key files), it would be included accordingly, but this operation returns only JSON metadata about keys.

Dependencies

  • Requires an API authentication token credential configured for the Gitea instance.
  • Needs the base URL of the Gitea server set in the credentials.
  • Depends on the Gitea REST API endpoint /repos/{owner}/{repo}/keys to fetch deploy keys.

Troubleshooting

  • Authentication errors: Ensure the API token has sufficient permissions to read repository deploy keys.
  • Invalid owner or repo: Verify that the owner and repository names are correct and accessible by the authenticated user.
  • Pagination issues: If no results appear, check if the page and limit parameters are set correctly; pages start at 1.
  • Filtering by key_id or fingerprint: If filtering yields no results, confirm the values exist for the given repository.

Links and References

Discussion