Portainer icon

Portainer

Interact with Portainer via API

Actions190

Helm → Helm User Repositories List

AI-generated

Overview

This node operation, Helm User Repositories List, retrieves a list of Helm repositories associated with a specific user. It is useful in scenarios where you want to programmatically access or manage the Helm chart repositories that a particular user has configured or has access to. For example, it can be used in CI/CD pipelines to fetch repository information before deploying Helm charts or in dashboards that display user-specific Helm repository data.

Properties

Name Meaning
Id The unique identifier of the user whose Helm repositories you want to list. This is a required numeric input.

Output

The output of this node operation will be a JSON array or object containing details about the Helm repositories linked to the specified user ID. Each item typically includes repository metadata such as repository name, URL, and possibly other configuration details relevant to Helm repositories.

If the node supports binary data output (not indicated here), it would generally represent files or charts fetched from the repositories, but based on the provided code and properties, the output is purely JSON data describing repositories.

Dependencies

  • Requires an API key credential for authentication to the Portainer API or the relevant service managing Helm repositories.
  • The node depends on the external Portainer API endpoint configured via credentials, which must be set up with the base URL and authentication token.
  • The bundled source code references an OpenAPI specification and uses an OpenAPI client library to interact with the API.

Troubleshooting

  • Common issues:
    • Invalid or missing user ID: Ensure the "Id" property is provided and corresponds to a valid user.
    • Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
    • Network or connectivity problems: Check the base URL and network access to the API server.
  • Error messages:
    • Unauthorized or 401 errors indicate invalid credentials.
    • 404 errors may mean the user ID does not exist or no repositories are found.
    • Timeout or connection refused errors suggest network issues or incorrect API endpoint configuration.

Links and References

Discussion