Allow blocked environment variables through if they're included explicitly in terminal launch configs · Microsoft/vscode#104154

(9 评论) (1 反应) (1 负责人)TypeScript (74,848 star) (10,221 fork)batch import

feature-requesthelp wantedterminal-process

描述

VSCode Version: 1.47.1 (not insider as I can't get docker builds working on that for some reason)
Local OS Version: Windows 10 2004
Remote OS Version: WSL2 Ubuntu 20.04
Remote Extension/Connection Type: Docker Desktop using WSL2 backend

Steps to Reproduce:

Create a new project with a single file:

# .devcontainer/devcontainer.json
{
  "image": "alpine:latest",
  "remoteEnv": {
    "GOOGLE_API_KEY": "api-key",
    "GOOGLE_SOMETHING_ELSE": "something-else"
  }
}

Rebuild and Reopen in Container
In the remote terminal, check the environment for variables:

$ printenv | grep GOOGLE

Expected outcome:

GOOGLE_API_KEY=api-key
GOOGLE_SOMETHING_ELSE=something-else

Actual outcome:

GOOGLE_SOMETHING_ELSE=something-else

This is the same no matter the base image used. Changing the name of GOOGLE_API_KEY to anything else, even by a single character, allows it through.

Does this issue occur when you try this locally?: Not relevant as this is a remote container build Does this issue occur when you try this locally and all extensions are disabled?: Not relevant as this is a remote container build

贡献者指南

技术栈: typescriptdocker
领域: developer experience
议题类型: bug
难度: 3
预计时间: 1-3 hours
活动状态: active
清晰度: clear
前置要求: understanding of VS Code remote containers
新手友好度: 40
研究方向: Investigate how VS Code filters environment variables in devcontainer configurations. The issue shows that variable names like 'GOOGLE API KEY' are blocked while others are not. Look at the remote container extension code that handles remoteEnv, particularly any blocklist logic. Check if the fix should allow explicit overrides or remove the blocklist altogether. The issue has comments and an assignee, so check for any linked PRs or ongoing work.