Is Azure Cli Command Synchronous or Asynchronous?

microsoft-azure

The Azure CLI (Command Line Interface) generally operates in a synchronous manner. This means when you issue a command, it will execute and return the output or an error before accepting the next command. You typically have to wait for the operation to complete before proceeding to the next step.

That said, there are certain operations (like creating a VM or starting a large database migration) that might take a considerable amount of time to complete. In such cases, you can run those commands in the background using different techniques, depending on the shell you are using, effectively making them asynchronous.

For example, in a Unix-like system, you can use “&” at the end of the command to run it in the background, or use the “nohup” command to make sure the command continues to run even if your session disconnects.

In addition, some Azure services offer asynchronous operations through their APIs, which the Azure CLI can leverage. For instance, many long-running operations return an operation ID that you can use to poll for the status of the operation.

Keep in mind that running a command in the background or leveraging asynchronous APIs is not the same as the Azure CLI inherently being asynchronous; these are just techniques to manage long-running operations effectively.

–EOF (The Ultimate Computing & Technology Blog) —