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 integrates with the Doppler API to manage various resources related to projects, configurations, secrets, environments, and more. Specifically, for the Environment resource with the Retrieve operation, it fetches detailed information about a specific environment within a given project.
Common scenarios where this node is beneficial include:
- Automating retrieval of environment details in CI/CD pipelines.
- Synchronizing environment metadata across systems.
- Auditing or monitoring environment configurations programmatically.
For example, you might use this node to retrieve an environment named "production" from a project called "my-app" to verify its settings before deploying new code.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (string) of the project that contains the environment to retrieve. |
| Environment | The name (string) of the environment to retrieve within the specified project. |
Output
The node outputs JSON data representing the retrieved environment's details as returned by the Doppler API. This typically includes all metadata and configuration associated with the environment.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node makes HTTP GET requests to the Doppler API endpoint:
/v3/environments/environment. - The base URL for the API is
https://api.doppler.com. - Proper permissions on the Doppler account are necessary to access environment details.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key credential is correctly configured and has sufficient permissions.
- Invalid project or environment names: Double-check that the project and environment names are correct and exist in Doppler.
- Network issues or API downtime: Verify network connectivity and Doppler service status if requests fail.
- Error responses from API: The node will forward error messages from Doppler; common errors include 404 Not Found (if environment does not exist) or 401 Unauthorized (invalid credentials).