Description
When running aspire deploy targeting Azure Container Apps, the CLI performs an az account show check to verify the user is logged in. This check has a hard timeout of approximately 10 seconds that cannot be overridden.
On some machines, az account show can take 20-40 seconds due to factors outside the user's control (e.g., Windows Defender real-time scanning of Python's import chain, network latency to Azure AD for token refresh, etc.). When this happens, the Aspire CLI fails with a timeout error before az has a chance to respond.
Expected behavior
- The timeout for the
az login check should be configurable (e.g., via a CLI flag or environment variable)
- Or the default timeout should be more generous (e.g., 60 seconds)
- Or the check should be skippable with a flag like
--skip-login-check
Environment
- Aspire SDK: 13.2.1
- OS: Windows 11
- az CLI: 2.84.0 (Python 3.13.11)
- Target: Azure Container Apps (
addAzureContainerAppEnvironment)
Repro
- Have a machine where
az account show takes >10 seconds (common with large Python import chains + real-time AV scanning)
- Run
aspire deploy targeting ACA
- The deploy fails with a timeout before
az responds
Workaround
None known. Restarting the machine sometimes helps by clearing the AV scan cache, but the issue recurs.
Description
When running
aspire deploytargeting Azure Container Apps, the CLI performs anaz account showcheck to verify the user is logged in. This check has a hard timeout of approximately 10 seconds that cannot be overridden.On some machines,
az account showcan take 20-40 seconds due to factors outside the user's control (e.g., Windows Defender real-time scanning of Python's import chain, network latency to Azure AD for token refresh, etc.). When this happens, the Aspire CLI fails with a timeout error beforeazhas a chance to respond.Expected behavior
azlogin check should be configurable (e.g., via a CLI flag or environment variable)--skip-login-checkEnvironment
addAzureContainerAppEnvironment)Repro
az account showtakes >10 seconds (common with large Python import chains + real-time AV scanning)aspire deploytargeting ACAazrespondsWorkaround
None known. Restarting the machine sometimes helps by clearing the AV scan cache, but the issue recurs.