vagrant-azure 1.2.1 → 1.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 6988e9e6d5fd8d3f47e6388ba6d29de2e24859c5
-  data.tar.gz: 9c7a6571ee284d5adf5060b7dfa8de439a2bce55
+  metadata.gz: 3018a28257bdcc80821fc0dc9b6e290fe2b0d79d
+  data.tar.gz: 60f16bba7743198062f51d3bb03a570f81e5eb4a
 SHA512:
-  metadata.gz: a6fc94b5099e9e693fda510f0444823cffe584e8f9891da5ca51f6833653e67fc0824c1fb1e6f71ce42d91516878897686a35a4032e17f8d3af2ae11d02a45f9
-  data.tar.gz: 09a6e2436f4dbb220b57cd7daab62b64429e7e76a6dd1ed0781b9366510512dc93bc47e38ebffcd2f2927e3f50dbdf2b84ab1d898731bbcd14342df509884fd5
+  metadata.gz: 44b0eafc536da864f46dfb2dd75d9e6bd56348c672b30e2fbbbeaab1ed55f93ecf438c555b7de31873233b912179f5d0735bde5fcdc8003bb0c751551be9ed6a
+  data.tar.gz: bb14c60621a2608026f32ab19f6fe99b5cd5b48f70af961a37ebd1fe672f23fad979ce57d9a9767527d686a0bf1ad4d75318d0f795465eec9dfcc00a39591c62

data/README.md

@@ -1,13 +1,13 @@
 # Vagrant Azure Provider
 
-![Gem Version](https://badge.fury.io/rb/vagrant-azure.png)
+[![Gem Version](https://badge.fury.io/rb/vagrant-azure.png)](https://rubygems.org/gems/vagrant-azure)
 
 This is a [Vagrant](http://www.vagrantup.com) 1.7.3+ plugin that adds [Microsoft Azure](https://azure.microsoft.com)
 provider to Vagrant, allowing Vagrant to control and provision machines in Microsoft Azure.
 
 ## Usage
 
-Install Vagrant 1.6.0 or higher - [Download Vagrant](http://www.vagrantup.com/downloads.html)
+Install Vagrant 1.7.3 or higher - [Download Vagrant](http://www.vagrantup.com/downloads.html)
 
 Install the vagrant-azure plugin using the standard Vagrant 1.1+ installation methods. After installing the plugin, you can ```vagrant up``` and use ```azure``` provider. For example:
 
@@ -115,24 +115,18 @@ The vagrant-azure provide exposes a few Azure specific configuration options:
 * `tcp_endpoints` - To open any additional ports. E.g., `80` opens port `80` and `80,3389:53389` opens port `80` and `3389`. Also maps the interal port `3389` to public port `53389`
 
 ### Certificate Generation on Windows
-We will use `makecert.exe` distributed as part of the in the Windows 7 SDK.  The following commands will create the required certificates and insert them into the current user’s personal store.
+We will use `makecert.exe` distributed as part of the in the Windows 7 SDK.  The following commands will create the required certificate and insert it into the current user’s personal store.
 
-* makecert.exe -r -pe -a sha1 -n "CN=My Azure Management Certificate"
--ss My -sr CurrentUser -len 2048 -sky exchange -sp "Microsoft Enhanced RSA
-and AES Cryptographic Provider" -sy 24
-
-* makecert.exe -r -pe -a sha1 -n "CN=My Azure RDP Certificate" -ss My -sr CurrentUser -len 2048 -sky exchange -sp "Microsoft Enhanced RSA and AES Cryptographic Provider" -sy 24
-
-* makecert.exe -r -pe -a sha1 -n "CN=My Azure SSL Certificate" -ss My -sr CurrentUser -len 2048 -sky exchange -sp "Microsoft Enhanced RSA and AES Cryptographic Provider" -sy 24
+```
+makecert.exe -r -pe -a sha1 -n "CN=AzCert" -ss My -sr CurrentUser -len 2048 -sky exchange -sp "Microsoft Enhanced RSA and AES Cryptographic Provider" -sy 24
+```
 
 (In order to have more details with images in Windows)[http://blogs.msdn.com/b/cclayton/archive/2012/03/21/windows-azure-and-x509-certificates.aspx]
 
 ### Get Started with Publish Settings
 
-* To create a pfx from the publishsettings, simply download the publishsettings file for your subscription 
-[https://manage.windowsazure.com/publishsettings](https://manage.windowsazure.com/publishsettings/index?client=powershell). Make sure you have this gem installed and
- run `pfxer --in [path to your .publishsettings file]`. This will create a .pfx from your publish settings file which can 
- be supplied as a cert parameter for Service Management Commands.
+To create a pfx from the publishsettings, simply download the publishsettings file for your subscription 
+[https://manage.windowsazure.com/publishsettings](https://manage.windowsazure.com/publishsettings/index?client=powershell). Make sure you have the [Ruby Azure](https://rubygems.org/gems/azure/versions/0.7.0) gem installed and run `pfxer --in [path to your .publishsettings file]`. This will create a .pfx from your publish settings file which can be supplied as a cert parameter for Service Management Commands.
 
 ### Get Started with OpenSSL
 

data/lib/vagrant-azure/action/run_instance.rb

@@ -73,7 +73,7 @@ module VagrantPlugins
             # a deployment.
             if config.cloud_service_name && !config.cloud_service_name.empty?
               begin
-                cloud_service = ManagementHttpRequest.new(
+                cloud_service = Azure::BaseManagement::ManagementHttpRequest.new(
                     :get,
                     "/services/hostedservices/#{config.cloud_service_name}?embed-detail=true"
                 ).call

data/lib/vagrant-azure/version.rb

@@ -6,6 +6,6 @@
 
 module VagrantPlugins
   module WinAzure
-    VERSION = '1.2.1'
+    VERSION = '1.3.0'
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: vagrant-azure
 version: !ruby/object:Gem::Version
-  version: 1.2.1
+  version: 1.3.0
 platform: ruby
 authors:
 - MSOpenTech
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2015-08-17 00:00:00.000000000 Z
+date: 2015-10-06 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: azure