[Feature request] Allow the configuration of a custom timeout duration on `azd provision`

[GABRIELNGBTUC]

• Make sure you've installed the latest version using instructions

Output from azd version
azd version 1.23.0 (commit 9a02add)

Describe the issue
Currently there is a 20 minutes (for app service deployments) timeout on azd deployments. While it is good to have this timeout, the current duration is way too high for simple deployments in a pipeline environment. It would be great to be able to configure a shorter timeout to have faster feedback from the deployment.

Expected solution
The ability to run a command such as azd deploy service --fromPackage path --timeout timeInSeconds to configure the deployment timeout.

[kristenwomack]

We have a few things in progress to improve the speed of the feedback loop. Pulling this into our work priority and we'll let you know a few options for you to try.

[vhvb1989]

When azd deploys to App Service, it waits for the site status on Linux Web Apps.
See:

azure-dev/cli/azd/pkg/azsdk/zip_deploy_client.go

Line 181 in 6db9cd2

poller, err := client.BeginGetProductionSiteDeploymentStatus(retryCtx, resourceGroup, appName, deploymentStatusId, nil)

This kind of deployment ensures that azd deploy won't complete until the WebApp returns DeploymentBuildStatusRuntimeSuccessful (or an error).

The time to start a WebApp depends on the Web App SKU (how fast the HW is) and the application stat up.

Maybe for CI/CD deployments we don't need to wait for DeploymentBuildStatusRuntimeSuccessful and we can just return as soon as zip-deployment is completed (Like we do for Windows Web Apps). Or azd should have a switch/flag to disable waiting for the webApp to be started