Vagrant Azure Versions Save

This major release of Vagrant-Azure marks the move to Azure Resource Manager and template based deployment of Vagrant boxes. The release supports modern Azure networking and compute stacks as well as Managed Disks and custom VHDs.

• Added support for managed disks
• Added support for custom VHDs using managed VM image import
• Added support for managed image references
• Refactored templates into smaller chunks and started adding specs around them
• Added travis configuration with gem deployment
• Adding documentation for common scenarios
• Updated to the latest Azure Ruby SDK

Lock to Faraday 0.11.0 until ms_rest corrects an issue with ssl_options. See: https://github.com/Azure/vagrant-azure/issues/182#issuecomment-291606966

• require plugin version

• bug fix for reference to plugin version number

• Open of custom ranges of tcp endpoints #162
• Add user-agent into the ARM requests #163
• Add timestamp to deployment name #165

Thank you to @ddanciu, @matt-richardson and @vishrutshah

• #159 wait on all resources to deleted before ack'ing a destroy
• #136 adds availability sets functionality. Thank you to @codethestars for the contribution.

This release reintroduces Windows support. It also contains multiple fixes for issues #150, #153, #149, #147.

Notable Changes:

• Windows Support! Thank you, @matt-richardson!
• Updated dummy.box in the root of the repo
• Update the Azure SDK libs to 0.8.0
• Update to use Premium storage for faster deployments
• Don't wait on destruction of the resource group, but just issue the delete call
• Update the VM to Standard_DS2_v2 by default
• Don't default to NFS, but rather fall back to rsync by default
• Default admin username and password, which was causing failures when spinning up a default linux box
• Remove boot diagnostics from the VM to simplify the storage dependency and speed up provisioning

This release marks the first preview of Vagrant-Azure for Azure Resource Manager. Major changes:

• Azure Active Directory is the means of authentication, no more need for building a cert for Azure
• Simplified resource structure and templating for building VMs in Azure
• No multi box support (coming)
• No Windows support (coming)
• Azure will never see your private key. We only use your public key when making a new VM in Azure.

https://github.com/Azure/vagrant-azure/compare/v1.2.1...v1.3.0