localstack-azure-client: a cold first functionapp deploy times out at 300 s, and the hint names --no-wait

未关闭 适合新手
#112 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
活跃
技术栈
azure, typescript

调研方向

从 Issue 中提到的两个文件 output.ts 和 docs/AZURE.md 开始。检查超时提示如何说明 functionapp deploy 和 webapp deploy 支持的 async 标志,然后查看 Azure 部署指南。完成标准是:提示为两个命令都推荐 --async true,并且文档说明首次代码部署会下载构建映像和扩展包,耗时可能超过 300 秒。

由索引模型根据 Issue 内容生成。

描述

What happens

On a machine that has never deployed Function App code to the emulator, the first functionapp deploy makes the emulator:

  1. pull the Oryx build image mcr.microsoft.com/oryx/build:github-actions-debian-bookworm-20260415.1 (1.23 GB, amd64 only, so it runs emulated on arm64)
  2. cache the Functions extension bundle
  3. build the runtime image

Here that took about 38 minutes: 17 minutes for the pull, 16 for the extension bundle, and about 4 for the build. Without --async, the command hits the default LOCALSTACK_AZ_TIMEOUT_SECONDS of 300:

functionapp deploy --resource-group local-rg --name local-inventory-functionapp-test --src-path function/inventory_function.zip --type zip
❌ Command Timed Out

`az` did not finish within 300 s and was stopped; it may have changed the emulator already. For long operations raise LOCALSTACK_AZ_TIMEOUT_SECONDS, or use `--no-wait` where the command has it.

az functionapp deploy and az webapp deploy don't have --no-wait. Their flag is --async true. With the caches warm, the same deploy finishes in 1 minute 44 seconds.

Expected

  • The timeout hint (output.ts) should name --async true for functionapp deploy and webapp deploy.
  • docs/AZURE.md should mention that the first code deployment downloads the build image and the extension bundle once, and can take far longer than 300 s.

Context

  • MCP server 0.7.0 via npx
  • LocalStack Azure emulator 2026.11.0.dev501
  • OrbStack on Apple silicon
  • api-management-function-app sample from localstack-azure-samples
主要语言
TypeScript
星标
29
派生
14
平均合并
3 天 16 小时
30 天内合并 PR
18

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

localstack/localstack-mcp-server 的其他 Issue

查看 localstack/localstack-mcp-server 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。