DopplerHQ / DopplerHQ/cli

[BUG] `doppler secrets get` waits a few seconds before exiting

Open
#511 0 comments 0 reactions 1 assignee View on GitHub

@ryanrhanson is already working on this.

Since Feb 17, 2026.

bug
Dominant language
Go
Stars
396
Forks
83
Avg merge
1d 2h
Merged PRs (30d)
3

Description

Describe the bug
When I try to fetch an individual secret with doppler secrets get, the secret is printed quickly but then the process sometimes keeps running for 5-10 seconds before exiting. This makes scripts that rely on doppler secrets get very slow.

To Reproduce
Steps to reproduce the behavior. Please include output from running the command with --debug.

  1. Run time doppler secrets get TEST_SECRET_PLS_DELETE -p api-server --config prd --plain --debug (substitute secret, project, and config names that actually exist)

Output:

Debug: Using config dir /Users/ben/.doppler
Debug: Using config file /Users/ben/.doppler/.doppler.yaml
Debug: Reading config file
Debug: Retrieving token from system keyring
Debug: Sending anonymous analytics payload: '{"command":"doppler.secrets.get"}'
Debug: Performing HTTP POST to https://cli.doppler.com/v1/analytics
Debug: Performing HTTP GET to https://api.doppler.com/v3/configs/config/secrets?config=prd&include_dynamic_secrets=false&project=api-server&secrets=TEST_SECRET_PLS_DELETE
Debug: Request ID d735992d-8a53-4e76-b6fc-16180c00d512
test secret
doppler secrets get TEST_SECRET_PLS_DELETE -p api-server --config prd --plain  0.01s user 0.02s system 0% cpu 4.787 total

It prints all the output including the secret value very quickly, but intermittently it takes a very long time to exit (4.7 seconds in the above example)

Expected behavior
Doppler should immediately exit

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: macOS
  • Version 15.6

CLI Version:
Version 3.75.2

Additional context
Add any other context about the problem here.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.