Fix App Service deployment status hangs - #9489
Conversation
Treat five minutes without an App Service deployment status change as a non-fatal verification timeout. Preserve explicit deployment failures and surface the timeout as a warning from azd deploy and azd up. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: d0b31e7e-f0c1-430f-9533-2d7f32e2a4f0
|
Azure Pipelines: Successfully started running 1 pipeline(s). 21 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
Summary
azd deploy,azd up, and structured JSON outputImplementation notes
The timeout starts after the tracked zip deployment request is accepted. It measures time since the last deployment status transition rather than total elapsed time, allowing slow deployments to continue as long as App Service reports progress.
The existing production deployment status API remains the primary signal because it provides structured instance counts, errors, and failed-instance log URLs. Newer Site Status and startup-log APIs are not used because they are not yet consistently documented or available across App Service stamps.
Fixes #8687