microsoft / microsoft/vscode-remote-release
Allow specifying user environment variables for Remote - Containers
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
It would be very good if we could specify environment variables in the Remote - Containers Vscode settings level, so we could set passwords there for example, that would be automatically exposed to the containers, similarly with what happens today with Codespaces secrets set inside of GitHub configuration.
Contributor guide
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 with the Remote - Containers VS Code settings and compare them with the Codespaces secrets behavior described in the issue; no source files or tests are named. Done means users can specify environment variables at the settings level and have them exposed to containers, with the intended handling of passwords clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, vscode
- Domain
- developer-experience, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100