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!
The manual handling of personal branches for development often leads to a host of challenges. Teams frequently grapple with the cumbersome process of creating and deleting these branches, and resolving conflicts in config names. We often hear the need for more granular permissions so developers can’t see each other’s personal secrets. This not only consumes valuable time but also introduces potential for errors, confusion, non-ideal security stances, and inefficiencies, hindering both individual and team productivity.
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.
In dynamic team environments, keeping track of dismissed secrets can be a significant challenge, especially when multiple engineers are involved. It's easy for important details to be overlooked when a secret is dismissed and forgotten, leading to potential gaps in project management and security.
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.
Here's some stuff we're excited about as of late. Let us know what cool stuff you're building, reading, or even playing by replying to this email or posting in the Doppler Community, and we might feature your thing next month!
Stay up to date with new platform releases and get to know the team of experts behind them.