Changelog

Create Personal Configs and Manage Dismissed Secrets

As the year winds down and the chill sets in, we're heating things up with new updates. Dive in to discover how we're keeping your productivity hot even as the temperatures drop!

Create Personal Configs

Personal Configs are now available to users on all plans and are designed to alleviate these pain points by automatically creating a branch config for each developer that has access to that environment, such as the dev environment. This personal config is private, accessible only to that developer. Personal configs will also help standardize onboarding by allowing you to add a doppler.yaml file to your repo with dev_personal to auto-configure the Doppler CLI in development.

With Personal Configs automatically enabled in all new dev environments by default, the tedious tasks of manual creation, deletion, and conflict resolution of personal branches are a thing of the past. This not only streamlines your workflow but also bolsters security and individual efficiency, ensuring a smoother, more personalized, and conflict-free config management experience. Check out our documentation for more details and also learn how to enable Personal Configs on existing environments.

Manage Dismissed Secrets

To address this, we've introduced the ability to view and 'undo' dismissed secrets. This enhancement brings back crucial oversight, allowing you to easily manage and reintroduce previously dismissed secrets into the 'Action Required' section as well as a new Managed Dismiss Secrets option in the menu on each environment of a project. It's a vital step towards ensuring transparency and efficiency in your team's secrets management, keeping your projects streamlined and secure. Go the secrets editor page in a config to try it for yourself.

What else have we been up to?

• Creating a new role is now simpler with the ability to copy permissions from any existing built-in role. You can also compare the permissions of any role with those of another aiding in more precise access control.
• We’ve added new native sync integrations for Deno Deploy and Harness, making it even easier to manage your secrets within partner ecosystems.
• Kubernetes Operator v1.5.0 has been released with added support for syncing subsets of secrets from Doppler configs via a new secrets property.
• We've fixed a Preview Branch pagination issue with our Vercel integration sync that limited you to choosing from the first 20 branches. All preview branches are now selectable!
• Links in the Integration area of Workplace Settings now take you to the sync management page where you'll find the sync in question, improving workflow efficiency.
• Fixed an issue which was preventing AWS Postgres rotated secret integrations from being reconnected.
• Our React migration is in the final stages with our Integrations page now migrated to React. This expands on our commitment to improving site page performance.
• Fixed an issue where CircleCI syncs would fail with an Unknown Error (400) when attempting to sync to a standalone CircleCI organization with no external VCS attached.
• Improved secret value validation for AWS Parameter Store syncs enhancing visibility of potential issues and workflows.
• Enhanced sync integration error handling for both GitHub Actions and Vercel improving reliability.