You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current CLI provides waiting by default for each command. When --no-wait option is used, the CLI immediately returns back without displaying anything to the customer. If this is a long running action, the customer has no ability to retrieve the status of async command. Each command would need to use --debug to see 'Azure-AsyncOperation' header returned. This creates poor customer experience.
The proposal is to enhance command behavior for --no-wait.
Specifically, when the customer asks not to wait for the final result, the CLI should print a header back.
The text was updated successfully, but these errors were encountered:
The current CLI provides waiting by default for each command. When --no-wait option is used, the CLI immediately returns back without displaying anything to the customer. If this is a long running action, the customer has no ability to retrieve the status of async command. Each command would need to use --debug to see 'Azure-AsyncOperation' header returned. This creates poor customer experience.
The proposal is to enhance command behavior for --no-wait.
Specifically, when the customer asks not to wait for the final result, the CLI should print a header back.
The text was updated successfully, but these errors were encountered: