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

Open Beginner friendly
  • Is something wrong?
#112 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
azure, typescript
Domain
documentation, tooling

Research direction

Start with output.ts and docs/AZURE.md, the two files named in the issue. Check how the timeout hint describes supported async flags for functionapp deploy and webapp deploy, then review the Azure deployment guidance. Done when the hint recommends --async true for both commands and the docs explain that the first code deployment downloads the build image and extension bundle and can exceed 300 seconds.

Written by the indexing model from the issue text.

Description

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
Dominant language
TypeScript
Stars
29
Forks
14
Avg merge
3d 16h
Merged PRs (30d)
18

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from localstack/localstack-mcp-server

All issues in localstack/localstack-mcp-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.