Actions35
- Secret Actions
- Workplace Actions
- Workplace User Actions
- Workplace Role Actions
- Activity Log Actions
- Project Actions
- Project Role Actions
- Project Member Actions
- Config Actions
- Config Log Actions
- Environment Actions
- Trusted IP Actions
- Integration Actions
- Auth Actions
- Share Actions
Overview
This node interacts with the Doppler API to manage secrets within projects and configurations. Specifically, for the Secret resource and List operation, it lists all secrets associated with a specified project and configuration. This is useful when you want to retrieve an overview of all stored secrets in a particular environment or config setup.
Common scenarios include:
- Auditing or reviewing all secrets available in a project/config.
- Automating secret management workflows by fetching current secrets before updates.
- Integrating Doppler secrets into other automation pipelines.
Example: You have a project "MyApp" and a configuration "Production". Using this node, you can list all secrets stored under that config to verify or process them further.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (name or slug) of the project containing the secrets to list. |
| Config | The specific configuration name within the project from which to list secrets. |
Output
The node outputs JSON data representing the list of secrets retrieved from the Doppler API for the given project and config. Each item in the output typically contains details about a secret such as its name, value (if accessible), and metadata.
If the node supports binary data output, it would represent secret values or related files; however, based on the static code, only JSON output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node makes HTTP GET requests to the Doppler API endpoint
/v3/configs/config/secretswith query parameters forprojectandconfig. - No additional external dependencies are indicated.
Troubleshooting
- Empty results: Ensure the
ProjectandConfigfields are correctly set and correspond to existing resources in Doppler. - Authentication errors: Verify that the API key credential is valid and has sufficient permissions to list secrets.
- API request failures: Network issues or incorrect API base URL could cause failures; check connectivity and credentials.
- Encoding issues: The project and config names are URL-encoded; ensure no invalid characters cause malformed requests.
Links and References
- Doppler API Documentation (general reference for Doppler API endpoints)
- Doppler Secrets Management (for understanding secrets concepts)
Note: Internal credential names and exact parameter encoding details are abstracted per guidelines.