Add wait/no-wait support to Commands

[tjprescott]

PR #1463 added support for the ... wait command for select command groups and the --no-wait option for several long-running operations in those groups. This issue is for identifying and tracking which commands still need this functionality exposed. Please nominate additional commands to be given wait/no-wait capability in the comments.

Needed

• acr repository delete
• postgres server firewall-rule create/delete
• provider register [issue az provider register should provide wait / no-wait #1910] (from @yugangw-msft we probably can live with it, as it is not a common op)
• storage file|blob copy (i.e. wait until a copy operation is finished) [issue [Storage] Retrieving blob copy status #1787]

Completed

• sql server create (PR [SQL] Add wait/no-wait support for SQL server command group #9022)
• cdn endpoint purge (PR [CDN] Add --no-wait support to CDN endpoint commands. #8792)
• container start/restart (PR [Container] Support --no-wait on container start/restart. #8600)
• snapshot create (PR [Snapshot] Add wait/no-wait support for snapshots. #7836)
• local-gateway create/update/delete (PR Add wait commands and --no-wait support #2524)
• express-route create/update/delete (PR Add wait commands and --no-wait support #2524)
• vnet-gateway create/update/delete (PR Add wait commands and --no-wait support #2524)
• vmss create/update/delete/start/stop/deallocate/... (PR Add wait commands and --no-wait support #2524)
• vm delete/deallocate/start/stop/... (PR Add wait commands and --no-wait support #2524)
• vm user (PR Add wait commands and --no-wait support #2524)
• vm create/update (PR Support Wait/No-Wait #1463)
• group delete (PR Support Wait/No-Wait #1463)
• group deployment create (PR Support Wait/No-Wait #1463)
• application-gateway create/update/delete (PR Support Wait/No-Wait #1463)
• vnet-gateway create/update (PR Support Wait/No-Wait #1463)
• az disk commands (PR Add wait/no-wait support to "az disk" commands. #3390)
• network nic create (PR Add --no-wait support to various commands #6684)
• vm extension set (PR Add --no-wait support to various commands #6684)
• group deployment delete (PR Add --no-wait support to various commands #6684)

[derekbekoe]

This is needed for end of Sprint 12 right?
cc: @johanste, @yugangw-msft

[derekbekoe]

Removed milestone as this is an additive change.

[tjprescott]

I would think this is not really a GA-mandatory item. It would simply be an additive feature we can incrementally roll out over time. This issue is to track those items for which it would be nice to have.

[yangl900]

Please add support for "az vm access" as well, the command took minutes to complete, it's practically not possible to manage large set of VMs without --no-wait.

[jamescgibson]

I'd love to get --no-wait on az disk delete

[mrx88]

I would really like to get --no-wait for "az network nic create" and "am vm extension set" commands.

[weznagwama]

az group deployment delete --no-wait would be great, ATM there's no way to async delete a batch of deploys, have to serially do it one by one and it takes a long time.

[dcbrown16]

I have a customer request for --no-wait on az snapshot create. Thanks!

[razvangoga]

az postgres server firewall-rule create and az postgres server firewall-rule delete could use the same flag. I'm provisioning a PgSQL db with firewall rules from azure devops and from the ~8 mins pipeline run time ~4 are just to set 5 firewall rules

[emoscardini]

If possible, please add "az sig" to the list

[tehyatt]

I need wait for az acr network-rule add. It is not a long running operation, but it's long enough to fail in my use-case. I'm using terraform to a list of outbound IP addresses from an app service to the existing list of on-premise IPs. Terraform doesn't support modifying that list after creation of the acr (see hashicorp/terraform-provider-azurerm#4936). So I'm using a null resource with a provisioner. But it launches all the az commands without waiting, and so some of them fail with "Error: Error running command 'az acr network-rule add --name registryname --ip-address xxx.xxx.xxx.xxx': exit status 1. Output: ERROR: Another operation is in progress for the resource /subscriptions/****/resourceGroups/rg-name/providers/Microsoft.ContainerRegistry/registries/registryname. Please try after some time."

[GitMrZ]

Need a wait option on:
az network dns zone delete

I keep my zone data in the flat file format to feed internal DNS servers. The delete can take a few seconds or several minutes for a 400 record zone. Obviously do not want zone down long. THX.

[naammeinkyahai]

Please add the ability to --no-wait for az postgres db delete

[adamrushuk]

Please add --no-wait support for az image delete?

[ghost]

I need a wait option for storage account. I'm having issues creating a container right after the storage account is created using az cli.

#!/usr/bin/env bash

az storage account create \
  --name "samassimoarm" \
  --resource-group "rgMassimoTf" \
  --location "South Central US" \
  --default-action 'Allow' \
  --sku Standard_LRS


while true; do
  PROVISIONED=`
    az storage account show \
      --name "samassimoarm" \
      --resource-group "rgMassimoTf" \
      --query [provisioningState] \
      --output tsv
  `

  [[ $PROVISIONED == 'Succeeded' ]] && break
done

CONNECTION_STRING=`
  az storage account show-connection-string \
    --name "samassimoarm" \
    --resource-group "rgMassimoTf" \
    --output tsv
`

az storage container create \
  --name "arm-templates" \
  --account-name "samassimoarm" \
  --connection-string "$CONNECTION_STRING"

[sdavis3]

az vm run-command needs --no-wait option.

Example command:

az vm run-command invoke -g rgName -n vmName --no-wait --command-id RunPowerShellScript --scripts @c:\temp\run_this_script.ps1

[zhoxing-ms]

@sdavis3 If you have new requirements, please create a feature request. We will arrange our development plan according to the priority.

[michelletaal-shell]

I'd also like to nominate az sql db import/export for a no-wait
But, I would highly suggest to actually add this flag as an option to all existing commands as a global parameter.

Flagged in #23885

[darkoa-msft]

What about mandating wait support for any API that returns 202?
I do not understand how this issue can be open for 8 years.