* Rename microsoftopentechnologies -> microsoft namespace
* slave -> agent refactor (strings, classes, and variable names where possible)
* Token cache file name should be specific to cloud name
* Make the resource group configurable
* Update SDK to 0.9.4
* Fix: Token expiration was incorrectly calculated (API is named a bit oddly).
* Fix: Token expiration is in seconds.
* Change VM/deployment names to ones that are valid
* Fix location + VM sizes
It appears that that the location and VM size APIs do not currently support the AAD based authentication. The certificate is required. Rather than re-introduce the cert for just this limited UI scenario, I have decided to hard-code the list based on the returned info from current Azure. This is a decent short term solution, since a move to the 1.0.0 API (when released) will require that this code be changed anyway and presumably this problem should be fixed for good at that point.
* Proper handling for custom image URIs
* Asynchronous verification of the subscription info
* Asynchronous verification of the azure templates
* Asynchronous provisioning
* Clean up resources after unsuccessful provisioning
* Lots of logging updates
* Fix: SSH launcher - Get channels before connection for exec channels
Getting the channels after connection introduces a race where we could potentially fail to read from the input streams if they were obtained from the channel after the connection had completed.
* Add diagnostics to image verification messages
* Asynchronous deletion via UI
* Update version of Jsch
* Temporarily disable image verification for reference images
* Allow for initialization scripts to be run as root
* Cleanup of slaves now works properly
* Doesn't clean up when node is taken offline by user
* Post build tasks won't kill other runs or show errors in the job logging
* Retention strategy now for online nodes, cleanup for offline nodes
* Nodes that are marked to shut down on idle can now be restarted properly (before too many could be started)
* Add option to treat failures of the initialization script as a reason to discard the VM (linux only currently)
* Reenable Windows custom script extension for startup
* Update documentation with new sample startup scripts
Add setAcceptingTasks appropriately
doc fixup
Getting the channels after connection introduces a race where we could potentially fail to read from the input streams if they were obtained from the channel after the connection had completed.
It appears that that the location and VM size APIs do not currently support the AAD based authentication. The certificate is required. Rather than re-introduce the cert for just this limited UI scenario, I have decided to hard-code the list based on the returned info from current Azure. This is a decent short term solution, since a move to the 1.0.0 API (when released) will require that this code be changed anyway and presumably this problem should be fixed for good at that point.
