Doppler

Overview

This node interacts with the Doppler API to manage configurations within projects. Specifically, for the Config resource and the Delete operation, it deletes a specified configuration from a given project. This is useful when you want to programmatically remove obsolete or unwanted configuration sets from your Doppler-managed projects.

Practical examples include:

• Automating cleanup of old configurations during CI/CD pipelines.
• Removing test or temporary configurations after deployment.
• Managing environment-specific configurations by deleting those no longer needed.

Properties

Output

The node outputs the JSON response returned by the Doppler API after attempting to delete the configuration. Typically, this will confirm successful deletion or provide error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

• Requires an API authentication token credential configured in n8n to authenticate requests to the Doppler API.
• The node sends HTTP DELETE requests to the Doppler API endpoint /v3/configs/config with query parameters specifying the project and config names.

Troubleshooting

• Common issues:

  • Providing incorrect or misspelled project or config names will result in errors or no action.
  • Lack of proper API credentials or expired tokens will cause authentication failures.
  • Attempting to delete a locked or protected configuration may fail if the API enforces such restrictions.

• Error messages:

  • Authentication errors typically indicate missing or invalid API keys; ensure credentials are correctly set up.
  • "Not Found" errors suggest the specified project or config does not exist; verify input values.
  • Permission denied errors mean the API user lacks rights to delete the config; check user permissions in Doppler.

Links and References

• Doppler API Documentation
• Doppler Configurations API