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 interact with configuration logs among other resources. Specifically, for the "Config Log" resource and the "List" operation, it retrieves a list of all configuration logs associated with a specified project and configuration. This is useful for auditing changes, tracking history, or monitoring configuration updates within a project.
Practical examples include:
- Fetching recent configuration changes to review what was modified.
- Auditing configuration logs before deploying new versions.
- Monitoring configuration activity for compliance or troubleshooting.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (string) of the project whose configuration logs you want to list. |
| Config | The identifier (string) of the specific configuration within the project to list logs for. |
Output
The output JSON contains an array of configuration log entries retrieved from the Doppler API endpoint /v3/configs/config/logs. Each entry represents a single configuration log record related to the specified project and config. The exact structure of each log entry depends on the Doppler API response but typically includes details such as timestamps, user actions, and change descriptions.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node uses the base URL
https://api.doppler.comfor requests. - Proper permissions on the Doppler account to access project configuration logs are necessary.
Troubleshooting
- Empty or no logs returned: Verify that the project and config identifiers are correct and that there are existing logs for them.
- Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
- API rate limits: If many requests are made in a short time, Doppler may throttle responses; implement retry logic or reduce request frequency.
- Malformed parameters: Make sure the project and config names are properly URL encoded and correctly inputted.