[BUG] Doppler cli can't find secret when both --only-secrets and --name-transformer flags are defined
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 396
- Forks
- 83
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 3
Description
Describe the bug
When I use both --only-secrets and --name-transformer flags with doppler run, it's not working and reporting that secret not exist:
❯ doppler run --only-secrets SOME_SECRET --name-transformer tf-var -- env
Doppler Error: the following secrets you are trying to include do not exist in your config:
- SOME_SECRET
To Reproduce
Run doppler run with both flags --only-secrets and --name-transformer to see the issue.
Expected behavior
I expect to get single secret transformed into terraform variable format.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [macOS]
- Version [13.3]
CLI Version:
Version v3.56.2
Additional context
Doppler run works for this secret as soon I remove --name-transformer flag
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the doppler run command and reproduce the behavior with --only-secrets SOME_SECRET --name-transformer tf-var -- env. Trace how these two flags are processed together, then verify that the single secret is found and exposed in Terraform-variable format while the existing behavior without --name-transformer remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100