localstack-azure-client: .bicepparam files that use readEnvironmentVariable() can't be deployed
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 64/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- azure, typescript
调研方向
Start with child-env.ts to see how the Azure CLI environment allow-list is built, then read docs/AZURE.md and the tool description. Document that variables are not forwarded and .bicepparam files using readEnvironmentVariable() need inline --parameters, or explore a setting for explicitly forwarded variables while blocking Azure credential prefixes. Done means the limitation and supported behavior are clear, with any forwarding option preserving the stated credential restrictions.
由索引模型根据 Issue 内容生成。
描述
What happens
The Azure tool builds az's environment from an allow-list (child-env.ts). That's the right call for keeping az away from real Azure, but it also means a .bicepparam file that reads a value with readEnvironmentVariable() can't be deployed through the tool:
deployment group validate --resource-group local-rg --template-file bicep/main.bicep --parameters bicep/main.bicepparam
❌ Command Failed (exit 1)
ERROR: …/bicep/main.bicepparam(11,47) : Error BCP427: Environment variable "BACKEND_SECRET" does not exist and there's no default value set.
The api-management-function-app sample in localstack-azure-samples does this: its deploy.sh exports BACKEND_SECRET before calling az. Through the MCP tool there is no way to set it, so an agent has to drop the .bicepparam file and pass --template-file main.bicep --parameters backendSecret=…. That puts the secret in the agent's transcript.
Expected
At least, docs/AZURE.md and the tool description should say that the environment isn't forwarded and that .bicepparam files using readEnvironmentVariable() need inline --parameters instead.
A possible option is a setting that names extra variables to forward to az, while still refusing AZURE_*, ARM_* and MSI_*. That would also keep secrets out of tool-call arguments.
Context
- MCP server 0.7.0 via npx
- LocalStack Azure emulator 2026.11.0.dev501
- Bicep 0.48.1
- Azure CLI 2.70.0
- 主要语言
- TypeScript
- 星标
- 29
- 派生
- 14
- 平均合并
- 3 天 16 小时
- 30 天内合并 PR
- 18
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
localstack/localstack-mcp-server 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
localstack/localstack-mcp-server#112 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
localstack/localstack-mcp-server#110 ·
维护者通常 1 天内回复
-
Azure weekly suite failing可能重新可做 @HarshCasper 于 28 天前认领，目前没有进行中的 PR。 未关闭
localstack/localstack-mcp-server#83 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Deployer health check blocks deploys to remote/ephemeral instances (requires a local gateway)可能已有人在做 @missusk 于 63 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 55/100
localstack/localstack-mcp-server#70 ·
维护者通常 1 天内回复
-
Inconsistent container name between `lstk` (`localstack-aws`) and MCP (`localstack-main`)可能已有人在做 @jhubbardsf 于 192 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 55/100
localstack/localstack-mcp-server#25 ·
维护者通常 1 天内回复
查看 localstack/localstack-mcp-server 的全部 Issue
相似的 Issue
-
check:passed streams:add
难度 1/5 1 小时以内 新手友好度 65/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
GiganticMinecraft/seichi-playguide#183 ·
维护者通常 1 天内回复
-
area: core complexity: easy impact: medium
难度 2/5 1-3 小时 新手友好度 86/100
ueberdosis/tiptap#8668 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
longbridge/nsh#804 ·
维护者通常 1 天内回复