[FEATURE] Automatically source env on terminal open in VSCode
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 wouldn't say that I like typing "doppler run " each time I use my CLI.
Describe the solution you'd like
I would like to have a doppler source command to source environment variables to the local terminal.
I would also like to have a VSCode or ZSH integration that would do that for me.
Describe alternatives you've considered
I wrote this command to download and source secrets to the local terminal:
eval $(doppler secrets download --format env --no-file --fallback-only)
I am still wondering how to run a command on each ZSH terminal open.
Final solution for me
I've created an alias that I run each time I want to seed environment variables to the current terminal:
alias denv="eval \$(doppler secrets download --format env --no-file --fallback-only)"
Then, I can call it like this:
denv
Additional context
My IDE is VSCode.
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
The issue names no implementation files or tests. Start by locating the CLI command entry points and assessing the VSCode and ZSH integration requirements. Done means defining and implementing the requested environment-sourcing behavior with a clear way to verify it in each supported terminal context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, vscode, zsh
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100