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 configurations within a specified project. Specifically, the "Lock" operation on the "Config" resource prevents a configuration from being renamed or deleted, effectively making it immutable until unlocked. This is useful in scenarios where you want to protect critical configuration settings from accidental changes or deletions, such as production environment variables or sensitive deployment parameters.
Practical examples:
- Locking a configuration after finalizing its values for a production release.
- Preventing deletion of important config sets that multiple services depend on.
- Temporarily locking configs during maintenance windows to avoid unintended modifications.
Properties
| Name | Meaning |
|---|---|
| Project | The identifier (name or slug) of the project containing the configuration to lock. |
| Config | The name of the specific configuration within the project to be locked. |
Output
The node outputs the JSON response returned by the Doppler API after attempting to lock the specified configuration. This typically includes confirmation details about the locked config or any error messages if the operation failed.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the Doppler API.
- The node sends HTTP POST requests to the Doppler API endpoint
/v3/configs/config/lockwith query parameters specifying the project and config names. - n8n must be configured with valid Doppler API credentials to authorize these requests.
Troubleshooting
Common issues:
- Invalid or missing project or config names will cause the API to reject the request.
- Insufficient permissions associated with the API key may prevent locking.
- Network connectivity problems can cause request failures.
Error messages:
- Errors indicating "config not found" suggest incorrect project or config identifiers.
- Authorization errors imply invalid or expired API credentials.
- Rate limiting or server errors from Doppler should be retried later.
To resolve:
- Verify the project and config names are correct and exist in Doppler.
- Ensure the API key has sufficient permissions.
- Check network connectivity and retry if transient errors occur.
Links and References
- Doppler API Documentation
- Doppler Config Lock Endpoint (for detailed API usage)