3.2.0
This release brings more verbose error logging to the doppler run command. We think users are going to want to see these errors if they occur, which is why they're enabled by default. Not interested in transient errors? Just call doppler run with --silent to silence them.
Changelog
b02aa17 Add additional internal logging functions
fa2d58c Always log failed update checks in debug mode
4f249a0 Globally recognize the --silent flag
9488fc9 Increase the verbosity of the doppler run command
a7dbbae Print individual file names during doppler run cleanup dry run
051529d Remove unused variable
a35ab11 Silence run command error output with --silent-exit
Docker images
docker pull dopplerhq/cli:3.2.0docker pull dopplerhq/cli:3.2docker pull dopplerhq/cli:3docker pull dopplerhq/cli:latestdocker pull gcr.io/dopplerhq/cli:3.2.0docker pull gcr.io/dopplerhq/cli:3.2docker pull gcr.io/dopplerhq/cli:3docker pull gcr.io/dopplerhq/cli:latestdocker pull dopplerhq/cli:3.2.0-nodedocker pull dopplerhq/cli:3.2-nodedocker pull dopplerhq/cli:3-nodedocker pull dopplerhq/cli:nodedocker pull gcr.io/dopplerhq/cli:3.2.0-nodedocker pull gcr.io/dopplerhq/cli:3.2-nodedocker pull gcr.io/dopplerhq/cli:3-nodedocker pull gcr.io/dopplerhq/cli:nodedocker pull dopplerhq/cli:3.2.0-rubydocker pull dopplerhq/cli:3.2-rubydocker pull dopplerhq/cli:3-rubydocker pull dopplerhq/cli:rubydocker pull gcr.io/dopplerhq/cli:3.2.0-rubydocker pull gcr.io/dopplerhq/cli:3.2-rubydocker pull gcr.io/dopplerhq/cli:3-rubydocker pull gcr.io/dopplerhq/cli:rubydocker pull dopplerhq/cli:3.2.0-pythondocker pull dopplerhq/cli:3.2-pythondocker pull dopplerhq/cli:3-pythondocker pull dopplerhq/cli:pythondocker pull gcr.io/dopplerhq/cli:3.2.0-pythondocker pull gcr.io/dopplerhq/cli:3.2-pythondocker pull gcr.io/dopplerhq/cli:3-pythondocker pull gcr.io/dopplerhq/cli:python