Removal of Deprecated Clients

reading time 5 mins

The doppler.sh script, Node.js CLI, and packages for Node.js, Python, and Ruby served us well in our earlier days, but it's time for them to be removed and replaced by our new Doppler CLI.

Migration instructions are below and we'll do our best to make things as quick and easy as possible.

New Doppler CLI Overview

The new Doppler CLI is a standalone binary that works for every operating system and is installed as part of the build and deployment environment, instead of as an application dependency.

This means that Doppler secrets are now accessed as standard environment variables, removing any trace of Doppler from your application code.

We're here to do everything necessary to make migrating to our new CLI a breeze. And we know you're going to love it!

Why Now?

You might be thinking, "if it ain't broke, don't fix it", which we can understand. Unfortunately, these deprecated packages and doppler.sh script use legacy API endpoints that are proving to be more trouble than they're worth, as less than 1% of our traffic relies on them.

Plus, our customers using these legacy tools are missing out on the constant stream of new features added to our Doppler CLI, as well as better and more flexible workflows for accessing secrets in any language and every environment.

How Much Time Do I Have?

The removal process will be done in two stages:

  • January 15, 2021: Removal of Doppler client packages and Node.js CLI package
  • January 31, 2021: Removal of doppler.sh and legacy API endpoints

Removal of Doppler client packages and Node.js CLI package

Removing the Doppler client and Node.js CLI packages mean application builds will begin failing if any of these packages are still a dependency. Existing deployments will be unaffected as the legacy API endpoints are still available.

Removal of doppler.sh and legacy API endpoints

Active deployments still using doppler.sh, Doppler client package, or the Node.js CLI will begin failing as the endpoints will be taken offline EOD January 31, 2021 PST.

Migrating to the New Doppler CLI

Migrating to the new Doppler CLI is a three-step process:

  1. Install the Doppler CLI for local development, CI/CD (if applicable), and live environments such as staging or production. It works everywhere and is installed as a standalone binary.
  2. Create Service Tokens for each CI/CD and live environment to provide read-only access to a specific config.
  3. Change how secrets are provided to scripts and processes using the doppler run command.

πŸ“˜

Node.js CLI Migration Docs

Check out our Node.js CLI migration guide to learn how the old terminology and commands map to the new CLI.

Environment variables and .env files

The new Doppler CLI presumes your scripts and applications will access secrets via environment variables and not locally saved unencrypted files such as a .env file.

If you currently rely on .env files and can't migrate to use only environment variables, we recommend scheduling a call to figure out the most secure method of continuing to use .env files.

Need more help?

If you need additional help, use our in-product support, or schedule a call.

We're here to help you every step of the way!


Did this page help you?