[FEATURE] Allow specifying repo config file from CLI
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 396
- Forks
- 83
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 3
Description
Is your feature request related to a problem? Please describe.
I'd like to be able to specify a repo config file when running doppler setup so that I can easily switch between repo configs.
Describe the solution you'd like
A flag specific to doppler setup so that I can use a chosen repo config file.
# setup as usual (doppler.yaml)
doppler setup --no-interactive
# setup with chosen config (doppler.alternative.yaml)
doppler setup --no-interactive -f doppler.alternative.yaml
Describe alternatives you've considered
- Mostly of use when using the
--no-interactiveflag, but would save time when having to switch between large repo configs.
Additional context
Thanks!
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 CLI entry point and flag handling for doppler setup, then trace how the default repo config file is selected. Add support for choosing an alternative config file with the setup command, and verify both the default and -f doppler.alternative.yaml examples work with --no-interactive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100