Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to list the secrets configured for GitHub Actions in a specific repository. It is useful when you want to programmatically retrieve all the action secrets associated with a repository, for example, to audit or manage them via automation workflows.

Common scenarios include:

  • Auditing repository secrets to ensure compliance.
  • Integrating secret management into CI/CD pipelines.
  • Synchronizing secrets across multiple repositories.

Example: You can use this node to fetch all GitHub Actions secrets of a repository owned by "octocat" named "hello-world", then process or log them in your workflow.

Properties

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

Output

The output JSON contains a list of secrets configured for GitHub Actions in the specified repository. Each secret typically includes metadata such as its name and creation/update timestamps but does not expose the secret values themselves for security reasons.

If the node supports binary data output, it would generally be related to any attachments or files returned by the API, but in this case, the output is purely JSON metadata about secrets.

Dependencies

  • Requires an API authentication token credential with permission to access repository secrets.
  • The node communicates with the GitHub API endpoint for repository secrets.
  • Proper configuration of the base URL and authentication credentials is necessary.

Troubleshooting

  • Common issues:

    • Insufficient permissions: The API token must have appropriate scopes to read repository secrets.
    • Invalid repository or owner names: Ensure the owner and repo names are correct and accessible.
    • Pagination parameters: Incorrect page or limit values may result in empty responses.
  • Error messages:

    • Unauthorized or 403 Forbidden errors indicate missing or insufficient API permissions.
    • 404 Not Found errors suggest the repository or resource does not exist or is inaccessible.
    • Rate limiting errors may occur if too many requests are made in a short time; consider adding delays or handling retries.

Links and References

Discussion