Closed matthewtole closed 2 years ago
I'm not a Go expert, but I believe this line is the problem:
https://github.com/DopplerHQ/cli/blob/master/pkg/cmd/run.go#L225
The original environment is being appended to the new environment, which will overwrite any matching values in the environment.
Thanks for reporting this bug. We're currently investigating and will report back.
I've confirmed this issue and put up a fix. This change should ship tomorrow, May 6th, in v3.19.1. I've also added some tests to ensure this doesn't break again in the future.
v3.19.1 is now live with this fix. Apologies for the inconvenience.
Describe the bug
If you have an environment variable that matches a Doppler variable, using
doppler run
will choose the environment variable, not the Doppler one, even if you don't use the--preserve-env
flag.This is a regression introduced in 3.39.0
To Reproduce
doppler run node
and then log the environment variableExpected behavior
It should log the value from Doppler.
CLI Version: 3.39.0