Migrating from @dopplerhq/cli
reading time 5 mins
Migrating from the @dopplerhq/cli is simple and fast. Here you will learn about the new Enclave terminology and CLI commands.
If you are installing the new Doppler CLI through brew, make sure to update the link after the installation.
brew install dopplerhq/cli/doppler brew link --overwrite doppler
Some of the Doppler terminology has changed with the Enclave branding. Here is a list of those changes.
|stage||environment||Development, Staging, Production|
After installing the new Doppler CLI, your configuration (api key, pipeline, etc) will automatically be transferred over. If you are using the CLI for local development we highly recommend that you reauthenticate with the new
$ doppler login
The login command will generate a new API key just for your machine, which can be revoked at any time.
If you would like to use an existing service token, that's supported too. You can pass in the token via configuration file, command line flag, or environment variable.
All Enclave commands have been moved under the
|List of Projects|
|List of Environments|
|List of Configs|
|List of Secrets|
Enclave Project and Config
To match the new terminology, we need new flags and environment variables for specifying the Enclave project and config.
Updated over 2 years ago