Have you ever needed to combine secrets together? Maybe a shared hostname? Today you can reference secrets from within other secrets.
We've added support for setting up OTP via a manual key. This is in addition to the primary method of scanning a QR code. If you haven't set up OTP yet, try it out today!
The new Doppler CLI is written in Go to ensure it remains lightweight, incredibly fast, and compatible on any OS without dependencies. Plus, it ensures your secrets are always encrypted.
We've rolled out a bunch of UI improvements and paper cut fixes this month. Here are a few of the things the team has released so far:
We've reduced our total page size by ~98% and load time by ~35%. To accomplish this, we now cache all static, public assets for up to 1 year. Assets are also cached by our globally-distributed CDN, meaning assets will always be served from a location near you.
We content-address all of our static assets. This is a method of naming the asset based on its content, typically using a hash function. Content-addressing ensures immutability by guaranteeing that the asset's name changes whenever its content does. For example, instead of loading doppler-logo.png, we load something like doppler-logo-a24a706d.png.
This funky naming enables us to crank caching up to the max. We specify a cache policy of public, max-age=31536000, immutable, must-revalidate. Let's break down what this means:
Our users trust Doppler with their secrets. In return, Doppler trusts users to take account security seriously. After all, the most secure systems are still only as secure as their weakest link.
To help improve account security for all users, we'll now prompt you to set up 2FA on your next login. We'll also do so after performing a password reset.
This helps ensure your secrets are shielded from poor password hygiene, which is an ongoing goal of ours.
Ever wanted to compare your database url or any other secret across development to production? With the Compare Secret feature, you can!
See the changes your team makes whenever an Enclave config is updated! View the config log to go deeper into which values were modified.
This major release is packed with features for local development.
Here's one: doppler run now automatically keeps a local, encrypted backup of your secrets. If the Doppler API or your internet connection ever goes down, you'll still be able to boot your app.
Remember, the CLI only takes 3 steps to set up locally:
For a full list of new features and breaking changes, check out the release notes.
(Ok, we cheated on step 2 with the &&. But we also included the installation, which we could've left out, just to show you how easy that is too!)
Automate your infrastructure with webhooks from Doppler. Get notified when anything in your Enclave project changes.
Brownie Points: Doppler signs the webhook request with a secret you provide to verify it is coming from us.
Protect your account with OTP 2FA, an open standard for two-factor authentication.
To encourage best practices, service tokens are now only displayed once during initial creation. After creation, you'll need to generate a new service token to retrieve its value. This helps ensure that you're using a unique service token for each service.
We are excited to ship one of our most requested features: Renaming Secrets!
Have you ever needed to upload a multi-line secret like a certificate? Now you can today!