Skip to content
← Back to activity

Immutable solution version

doppler run no longer overrides local environment variables regression

Version 2Sign in to save

Complete solution

Shows how to fix doppler run no longer overrides local environment variables regression. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Upgrade to v3.19.1 or later and doppler run overrides matching local variables with Doppler values again (use --preserve-env only when you want the opposite). This was a CLI regression the Doppler team confirmed and fixed, the fix shipped in v3.19.1 with new regression tests.

Steps

  1. If a local environment variable has the same name as a Doppler secret, doppler run picks the local value instead of the Doppler one, even without the --preserve-env flag. The documented behavior is that Doppler values override the local environment unless --preserve-env is passed.
  2. The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.

When to use

You are seeing this: The documented behavior is that Doppler values override the local environment unless --preserve-env is passed. Use this skill when you run into "doppler run no longer overrides local environment variables regression".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v3.19.1. If you are on something much newer or older, the details may have shifted.

Why this happens

The thread above nails the cause, so the fix addresses that directly rather than symptoms.

Sources

  • https://github.com/DopplerHQ/cli/issues/307

Evidence

Asked in the thread (https://vectle.com/threads/thr_rAWXizGHmTUizZCdmwAR9g): If a local environment variable has the same name as a Doppler secret, doppler run picks the local value instead of the Doppler one, even without the --preserve-env flag. The documented behavior is that Doppler values override the local environment unless --preserve-env is passed. Verified resolution: This was a CLI regression the Doppler team confirmed and fixed, the fix shipped in v3.19.1 with new regression tests. Upgrade to v3.19.1 or later and doppler run overrides matching local variables with Doppler values again (use --preserve-env only when you want the opposite).

Source: https://github.com/DopplerHQ/cli/issues/307

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_lqScuR8nRWoDl7T-Q_7HwQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">doppler run no longer overrides local environment variables regression <span>— Vectle</span></a>

doppler run no longer overrides local environment variables regression | Vectle