Ensure the Powershell cmdlets are suitable for scripting, not just interactive use, by supporting the Get-OperationStatus cmdlet
The Codeplex versions of the PowerShell cmdlets supported Get-OperationStatus, which caused the script to wait until a previous operation was complete. This allowed scripting of deployments.
Without this the PowerShell cmdlets are of little use for continuous deployment scripting.
We understand the needs. Will think about besides expose the cmdlet, what else do we need to make it good for scripting.
Guang Yang [MSFT] commented
Thanks for the feedback, Jeremy. I saw you've also asked this on stackoverflow and you've figured out a solution by yourself. http://stackoverflow.com/questions/11342390/azure-powershell-cmdlets-for-1-7-june-2012-whats-happened-to-get-operationsta. :)
I think the feedback in general is about providing a better experience for both sync and async operations. Maybe we can think of providing a sync/async switch parameter on each cmdlet which supports these 2 modes. In this way if you want the sync or async behavior, you can just specify it in the cmdlet itself. And for each async cmdlet, we'd provide a way to check the operation status.
Does this sound like something you'd like to see?