Guang Yang [MSFT]
My feedback
-
3 votes
This is available via SDK today: http://go.microsoft.com/fwlink/?LinkID=331678&clcid=0x409 We are working on exposing the same thing via Powershell commandlets.
An error occurred while saving the comment -
5 votes
Thanks for the feedback. Let us investigate what options might exist, here.
An error occurred while saving the comment Guang Yang [MSFT]
commented
Move to virtual machine forum
-
8 votes
Ohhh, interesting. Let us follow-up on this request.
An error occurred while saving the comment Guang Yang [MSFT]
commented
Move to virtual machine forum since this is about having Windows Azure PowerShell available by default in VM.
-
19 votes
We understand the needs. Will think about besides expose the cmdlet, what else do we need to make it good for scripting.
An error occurred while saving the comment 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?
Move to virtual machine forum.