kitchen-azurerm 1.5.2 → 1.5.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 20aa37ca60b29d9b0902d8741de326baa5fbe19fde0d37a9874dac2191b97b1f
-  data.tar.gz: f219f48b5b966faf7033fe0f78d8dd2f7638c77118c66f8c6bbae7c53e9f939c
+  metadata.gz: '04287eb76a3ad593e18ca9036eee9bdb72dc6a6d67b32c2153cb9e58f862d4bc'
+  data.tar.gz: 8f2ea6bb99fd8b92522d304f0bcc8d7db5034edcf79bc8862ca9dbc67d188920
 SHA512:
-  metadata.gz: 1ca9ed3f8eb461263d65f752299e46aded16a7e9b4fd3b73a06f66bacabd7ad5c7e566be1bfc299ed9abb0514ad386807b713bdf3740969883595a64a6afb7a0
-  data.tar.gz: 95988ebe08533122dc27d847cc817e799f07b72e4e13666170d6515bd9b9db5e37d6568722892f30388713ce9227653e04b72899c8d7f8d657fc83f078ca12b9
+  metadata.gz: c2f3c2f34b45368047be1397af798d77e1f0e8b6f58cc6121e4c250576b6be12d4166750ce8c08538d869576c142cd97eb99d2af9b185b21826065a0bc57a1e4
+  data.tar.gz: 519455de670f654930edafd819cc628f0de5ca069c97b8fe5dd750b50d9a3d771dd2db2f0260f1dc1e2e29e7e4fd307d802f71f2c28276a5d7bcc314da1c5cc3

data/README.md

@@ -1,6 +1,6 @@
 # kitchen-azurerm
 
-[![Gem Version](https://badge.fury.io/rb/kitchen-azurerm.svg)](https://badge.fury.io/rb/kitchen-azurerm) 
+[![Gem Version](https://badge.fury.io/rb/kitchen-azurerm.svg)](https://badge.fury.io/rb/kitchen-azurerm)
 ![CI](https://github.com/test-kitchen/kitchen-azurerm/workflows/CI/badge.svg?branch=master)
 
 **kitchen-azurerm** is a driver for the popular test harness [Test Kitchen](http://kitchen.ci) that allows Microsoft Azure resources to be provisioned before testing. This driver uses the new Microsoft Azure Resource Management REST API via the [azure-sdk-for-ruby](https://github.com/azure/azure-sdk-for-ruby).
@@ -77,9 +77,276 @@ wsus-windows-2019   Azurerm  ChefZero     Inspec    Winrm      <Not Created>  <N
 wsus-windows-2016   Azurerm  ChefZero     Inspec    Winrm      <Not Created>  <None>
 ```
 
-### .kitchen.yml example 1 - Linux/Ubuntu
+### Driver Properties
 
-Here's an example ```.kitchen.yml``` file that provisions an Ubuntu Server, using Chef Zero as the provisioner and SSH as the transport. Note that if the key does not exist at the specified location, it will be created. Also note that if ```ssh_key``` is supplied, Test Kitchen will use this in preference to any default/configured passwords that are supplied.
+The following properties are able to be specified in the `driver` section of the Test Kitchen configuration:
+
+#### subscription_id (required)
+
+* _string_ : Reads string from `ENV["AZURE_SUBSCRIPTION_ID"]` or must be specified if not present in `ENV`.
+  * Default Value: `ENV["AZURE_SUBSCRIPTION_ID"]`
+
+#### azure_environment
+
+* _string_ : Name of Azure environment to use.
+
+#### machine_size (required)
+
+* _string_ : Machine size to use for instances created.
+
+#### location (required)
+
+* _string_ : Azure location to use, example `"Central US"`
+
+#### azure_resource_group_prefix
+
+* _string_ : Prefix to use for the resource group configuration which will be created.
+  * Default Value: `"kitchen-"`
+
+#### azure_resource_group_suffix
+
+* _string_ : Optional suffix to append to resource group name.
+  * Default Value: `""`
+
+#### azure_resource_group_name
+
+* _string_ : Optional override for base name of the Azure Resource group which is created, uses prefix and suffix.
+  * Default Value: `""`
+
+#### explicit_resource_group_name
+
+* _string_ : Optional explicit resource group name, does not use `azure_resource_group_prefix`/`azure_resource_group_suffix`
+  * Default Value: `""`
+
+#### destroy_explicit_resource_group
+
+* _boolean_ : Used for cleanup with `explicit_resource_group_name`
+  * Default Value: `true`
+
+#### destroy_explicit_resource_group_tags
+
+* _boolean_ : Used for cleanup with `explicit_resource_group_name`
+  * Default Value: `true`
+
+#### destroy_resource_group_contents
+
+* _boolean_ : Can be used when you want to destroy the resources within a resource group without destroying the resource group itself. For example, the following configuration options used in combination would use an existing resource group (or create one if it doesn't exist) and will destroy the contents of the resource group in the ```kitchen destroy``` phase. If you wish to destroy the empty resource group created after you empty the resource group with this flag you can now set the ```destroy_explicit_resource_group``` to "true" to destroy the empty resource group.
+  * Default Value: `false`
+
+#### resource_group_tags
+
+* _hash_ : Optional hash of tags to pass to resource group
+
+  ```yaml
+  driver:
+    name: azurerm
+    resource_group_tags:
+      tag1: tag1value
+  ```
+
+#### image_urn
+
+* _string_ : Image URN to use for vm creation. List can be found using `az` cli - [https://docs.microsoft.com/en-us/azure/virtual-machines/linux/cli-ps-findimage#list-popular-images]
+  * Default Value: `"Canonical:UbuntuServer:14.04.3-LTS:latest"`
+
+#### image_url
+
+* _string_ : (unmanaged disks only) can be used to specify a custom vhd
+  * This VHD must be in the same storage account as the disks of the VM, therefore ```existing_storage_account_blob_url``` must also be set and ```use_managed_disks``` must be set to false.
+
+#### image_id
+
+* _string_ : (managed disks only) can be used to specify an image by id (managed disk). This works only with managed disks.
+
+#### use_ephemeral_osdisk
+
+* _boolean_ : Optional flag to use ephermeal disk for instances.
+  * Default Value: `false`
+
+#### os_disk_size_gb
+
+* _string_ : Optional override of os disk size for instances.
+
+#### os_type
+
+* _string_ : Should be specified when os type is not `linux`
+  * Default Value: `"linux"`
+
+#### custom_data
+
+* _string_ : Optional custom data which may be specified for instances [https://docs.microsoft.com/en-us/azure/virtual-machines/custom-data].
+  * Value can be a file or the data itself, this module handles base64 encoding for you.
+
+#### username
+
+* _string_ : Username to use for connecting to instances.
+  * Default Value: `"azure"`
+
+#### password
+
+* _string_ : Optional password to use for connecting to instances.
+  * Default Value: `SecureRandom.base64(25)` (Randomly generated 24 digit password)
+
+#### vm_name
+
+* _string_ : Optional name for vm instances to create.
+  * Default Value: `"vm"`
+
+#### nic_name
+
+* _string_ : Optional name to provide for nic, if not specified then nic name will be `"nic-#{config[:vm_name]}"`.
+
+#### vnet_id
+
+* _string_ : Optional `vnet` to provide.  If no `vnet` is chosen then public IP will be assigned using default values.
+
+#### subnet_id
+
+* _string_ : Optional subnet to provide, should be used with `vnet_id`.
+
+#### public_ip
+
+* _boolean_ : Option to specify if a public IP should be assigned.  In default configuration if all other options are left at default then a public IP _will_ be assigned, due to `vnet_id` having no value.
+  * Default Value: `false`
+
+#### public_ip_sku
+
+* _string_ : Optional string to change the SKU of allocated public IP address.  Defaults to `Basic`.
+  * Default Value: `"Basic"`
+
+#### storage_account_type
+
+* _string_ : Optional storage account type.
+  * Default Value: `"Standard_LRS"`
+
+#### existing_storage_account_blob_url
+
+* _string_ : Used with private image specification, the URL of the existing storage account (blob) (without container)
+
+#### existing_storage_account_container
+
+* _string_ : Used with private image specification, the Container Name for OS Images (blob)
+
+#### boot_diagnostics_enabled
+
+* _boolean_ : Whether to enable (true) or disable (false) boot diagnostics. Default: true (requires Standard storage).
+  * Default Value: `true`
+
+#### winrm_powershell_script
+
+* _string_ : By default on Windows machines, a PowerShell script runs that enables WinRM over the SSL transport, for Basic, Negotiate and CredSSP connections. To supply your own PowerShell script (e.g. to enable HTTP), use the `winrm_powershell_script` parameter. Windows 2008 R2 example:
+
+    ```yaml
+    platforms:
+    - name: windows2008-r2
+        driver_config:
+        image_urn: MicrosoftWindowsServer:WindowsServer:2008-R2-SP1:latest
+        winrm_powershell_script: |-
+            winrm quickconfig -q
+            winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="512"}'
+            winrm set winrm/config '@{MaxTimeoutms="1800000"}'
+            winrm set winrm/config/service '@{AllowUnencrypted="true"}'
+            winrm set winrm/config/service/auth '@{Basic="true"}'
+
+    ```
+
+#### pre_deployment_template
+
+* _string_ : Optional path to name of pre-deployment template to use.
+
+#### pre_deployment_parameters
+
+* _hash_ : Optional parameters to pass to pre-deployment template.
+
+#### post_deployment_template
+
+* _string_ : Optional path to name of post-deployment template to use.
+
+#### post_deployment_parameters
+
+* _hash_ : Optional parameters to pass to post-deployment template.
+
+#### plan
+
+* _hash_ : Optional JSON object which allows you to define plan information when creating VMs from Marketplace images. Please refer to [Deploy an image with Marketplace terms](https://aka.ms/azuremarketplaceapideployment) for more details. Not all Marketplace images support programmatic deployment, and support is controlled by the image publisher.
+
+#### vm_tags
+
+* _hash_ : Optional hash of vm tags to populate.
+
+#### use_managed_disks
+
+* _boolean_ : Must be set to `true` to use `data_disks` property.
+  * Default Value: `true`
+
+#### data_disks
+
+* _array_ : Additional disks to configure for instances.
+
+    ```yaml
+    platforms:
+    - name: windows2016-noformat
+    driver:
+        image_urn: MicrosoftWindowsServer:WindowsServer:2016-Datacenter:latest
+        data_disks:
+        - lun: 0
+            disk_size_gb: 128
+        - lun: 1
+            disk_size_gb: 128
+        - lun: 2
+            disk_size_gb: 128
+    ```
+
+#### format_data_disks
+
+* _boolean_ : Run format operations on attached data disks
+  * Default Value: `false`
+
+#### format_data_disks_powershell_script
+
+* _boolean_ : Customize the content of format operations for attached `data_disks`
+  * Default Value: `false`
+
+#### system_assigned_identity
+
+* _boolean_ : Whether to enable system assigned identity for the vm.
+  * Default Value: `false`
+
+#### user_assigned_identities
+
+* _hash_ : An object whose keys are resource IDs for user identities to associate with the Virtual Machine and whose values are empty objects, or empty to disable user assigned
+identities.
+
+#### deployment_sleep
+
+* _string_ : Time in seconds to sleep at the end of deployment before fetching details.
+  * Default Value: `10`
+
+#### secret_url
+
+* _string_ : used with connecting to Azure Key Vault
+
+#### vault_name
+
+* _string_ : used with connecting to Azure Key Vault
+
+#### vault_resource_group
+
+* _string_ : used with connecting to Azure Key Vault
+
+#### azure_api_retries
+
+* _string_ : Number of times to retry connections to Azure API.
+  * Default Value: `5`
+
+#### use_fqdn_hostname
+
+* _boolean_ : When true, Kitchen will use the FQDN that is assigned to the Virtual Machine. When false, kitchen will use the public IP address of the machine. This may overcome issues with Corporate firewalls or VPNs blocking Public IP addresses.
+  * Default Value: `false`
+
+### kitchen.yml example 1 - Linux/Ubuntu
+
+Here's an example ```kitchen.yml``` file that provisions an Ubuntu Server, using Chef Zero as the provisioner and SSH as the transport. Note that if the key does not exist at the specified location, it will be created. Also note that if ```ssh_key``` is supplied, Test Kitchen will use this in preference to any default/configured passwords that are supplied.
 
 ```yaml
 ---
@@ -103,8 +370,6 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchentesting::default]
     attributes:
 ```
 
@@ -116,9 +381,9 @@ Concurrent execution of create/converge/destroy is supported via the --concurren
 
 Where n is the number of threads to create. Note that any failure (e.g. an AzureOperationError) will cause the whole test to fail, though resources already in creation will continue to be created.
 
-### .kitchen.yml example 2 - Windows
+### kitchen.yml example 2 - Windows
 
-Here's a further example ```.kitchen.yml``` file that will provision a Windows Server 2019 [smalldisk] instance, using WinRM as the transport. An [ephemeral os disk](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks) is used. The resource created in Azure will enable itself for remote access at deployment time (it does this by customizing the machine at provisioning time) and tags the Azure Resource Group with metadata using the ```resource_group_tags``` property. Notice that the ```vm_tags``` and ```resource_group_tags``` properties use a simple ```key : value``` structure per line:
+Here's a further example ```kitchen.yml``` file that will provision a Windows Server 2019 [smalldisk] instance, using WinRM as the transport. An [ephemeral os disk](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks) is used. The resource created in Azure will enable itself for remote access at deployment time (it does this by customizing the machine at provisioning time) and tags the Azure Resource Group with metadata using the ```resource_group_tags``` property. Notice that the ```vm_tags``` and ```resource_group_tags``` properties use a simple ```key : value``` structure per line:
 
 ```yaml
 ---
@@ -146,12 +411,10 @@ platforms:
       name: winrm
 suites:
   - name: default
-    run_list:
-      - recipe[kitchentesting::default]
     attributes:
 ```
 
-### .kitchen.yml example 3 - "pre-deployment" ARM template
+### kitchen.yml example 3 - "pre-deployment" ARM template
 
 The following example introduces the ```pre_deployment_template``` and ```pre_deployment_parameters``` properties in the configuration file.
 You can use this capability to execute an ARM template containing Azure resources to provision before the system under test is created.
@@ -225,7 +488,7 @@ Example predeploy.json:
 }
 ```
 
-### .kitchen.yml example 4 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios)
+### kitchen.yml example 4 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios)
 
 The following example introduces the ```vnet_id``` and ```subnet_id``` properties under "driver" in the configuration file. This can be applied at the top level, or per platform.
 You can use this capability to create the VM on an existing virtual network and subnet created in a different resource group.
@@ -255,12 +518,10 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchen-azurerm-demo::default]
     attributes:
 ```
 
-### .kitchen.yml example 5 - deploy VM to existing virtual network/subnet with a Standard SKU public IP (use for ExpressRoute/VPN scenarios)
+### kitchen.yml example 5 - deploy VM to existing virtual network/subnet with a Standard SKU public IP (use for ExpressRoute/VPN scenarios)
 
 The following example introduces the ```vnet_id``` and ```subnet_id``` properties under "driver" in the configuration file. This can be applied at the top level, or per platform.
 You can use this capability to create the VM on an existing virtual network and subnet created in a different resource group.
@@ -293,12 +554,10 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchen-azurerm-demo::default]
     attributes:
 ```
 
-### .kitchen.yml example 6 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios) with Private Managed Image
+### kitchen.yml example 6 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios) with Private Managed Image
 
 This example is the same as above, but uses a private managed image to provision the vm.
 
@@ -328,12 +587,10 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchen-azurerm-demo::default]
     attributes:
 ```
 
-### .kitchen.yml example 7 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios) with Private Classic OS Image
+### kitchen.yml example 7 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios) with Private Classic OS Image
 
 This example a classic Custom VM Image (aka a VHD file) is used. As the Image VHD must be in the same storage account then the disk of the instance, the os disk is created in an existing image account.
 
@@ -371,12 +628,10 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchen-azurerm-demo::default]
     attributes:
 ```
 
-### .kitchen.yml example 8 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios) with Private Classic OS Image and providing custom data and extra large os disk
+### kitchen.yml example 8 - deploy VM to existing virtual network/subnet (use for ExpressRoute/VPN scenarios) with Private Classic OS Image and providing custom data and extra large os disk
 
 This is the same as above, but uses custom data to customize the instance.
 
@@ -416,12 +671,10 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchen-azurerm-demo::default]
     attributes:
 ```
 
-### .kitchen.yml example 9 - Windows 2016 VM with additional data disks
+### kitchen.yml example 9 - Windows 2016 VM with additional data disks
 
 This example demonstrates how to add 3 additional Managed data disks to a Windows Server 2016 VM. Not supported with legacy (pre-managed disk) storage accounts.
 
@@ -453,12 +706,10 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchentesting::default]
     attributes:
 ```
 
-### .kitchen.yml example 10 - "post-deployment" ARM template with MSI authentication
+### kitchen.yml example 10 - "post-deployment" ARM template with MSI authentication
 
 The following example introduces the ```post_deployment_template``` and ```post_deployment_parameters``` properties in the configuration file.
 You can use this capability to execute an ARM template containing Azure resources to provision after the system under test is created.
@@ -490,8 +741,6 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchen-azurerm-demo::default]
     attributes:
 ```
 
@@ -544,7 +793,7 @@ Example postdeploy.json to enable MSI extention on VM:
 }
 ```
 
-### .kitchen.yml example 11 - Enabling Managed Service Identities
+### kitchen.yml example 11 - Enabling Managed Service Identities
 
 This example demonstrates how to enable a System Assigned Identity and User Assigned Identities on a Kitchen VM.
 Any combination of System and User assigned identities may be enabled, and multiple User Assigned Identities can be supplied.
@@ -575,12 +824,10 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchentesting::default]
     attributes:
 ```
 
-### .kitchen.yml example 12 - deploy VM with key vault certificate
+### kitchen.yml example 12 - deploy VM with key vault certificate
 
 This following example introduces ```secret_url```, ```vault_name```, and ```vault_resource_group``` properties under "driver" in the configuration file. You can use this capability to create a VM with a specified key vault certificate.
 
@@ -606,8 +853,6 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[kitchentesting::default]
     attributes:
 ```
 
@@ -617,7 +862,7 @@ Starting with v0.9.0 this driver has support for Azure Government and Sovereign
 
 Note that the ```use_managed_disks``` option should be set to false until supported by AzureUSGovernment.
 
-### Example .kitchen.yml for Azure US Government cloud
+### Example kitchen.yml for Azure US Government cloud
 
 ```yaml
 ---
@@ -644,8 +889,6 @@ platforms:
 
 suites:
   - name: default
-    run_list:
-      - recipe[vmtesting::default]
 ```
 
 ### How to retrieve the image_urn
@@ -683,70 +926,6 @@ data:    Canonical  UbuntuServer  15.10-DAILY        15.10.201509220  westeurope
 info:    vm image list command OK
 ```
 
-### Additional parameters that can be specified in your `kitchen.yml` or added to your personal `kitchen.local.yml`
-
-* Note that the ```driver``` section can also take explicit values for ```username``` and ```password```. Otherwise, the default username is "azure" and the password is a randomly generated 24 character password that can be found in your local kitchen state file (typically `.kitchen/<instance-name>.yml`) if you require it for any reason.
-
-* The ```storage_account_type``` parameter defaults to 'Standard_LRS' and allows you to switch to premium storage (e.g. 'Premium_LRS')
-
-* The ```enable_boot_diagnostics``` parameter defaults to 'true' and allows you to switch off boot diagnostics in case you are using premium storage.
-
-* The optional ```vm_tags``` parameter allows you to define key:value pairs to tag VMs with on creation.
-
-* The optional ```plan``` parameter allows you to define plan information when creating VMs from Marketplace images. Please refer to [Deploy an image with Marketplace terms](https://aka.ms/azuremarketplaceapideployment) for more details. Not all Marketplace images support programmatic deployment, and support is controlled by the image publisher.
-
-* Managed disks are now enabled by default, to use the Storage account set ```use_managed_disks``` (default: true).
-
-* The ```image_url``` (unmanaged disks only) parameter can be used to specify a custom vhd (This VHD must be in the same storage account as the disks of the VM, therefore ```existing_storage_account_blob_url``` must also be set and ```use_managed_disks``` must be set to false)
-
-* The ```image_id``` (managed disks only) parameter can be used to specify an image by id (managed disk). This works only with managed disks.
-
-* The ```existing_storage_account_blob_url``` can be specified to specify an url to an existing storage account (needed for ```image_url```)
-
-* The ```custom_data``` parameter can be used to specify custom data to provide to the instance. This can be a file or the data itself. This module handles base64 encoding for you.
-
-* The ```os_disk_size_gb``` parameter can be used to specify a custom os disk size.
-
-* The ```azure_resource_group_prefix``` and ```azure_resource_group_suffix``` can be used to further disambiguate Azure resource group names created by the driver.
-
-* The ```explicit_resource_group_name``` and ```destroy_explicit_resource_group``` (default: "true") parameters can be used in scenarios where you are provided a pre-created Resource Group. Example usage: ```explicit_resource_group_name: kitchen-<%= ENV["USERNAME"] %>```. The ```destroy_explicit_resource_group``` option can now be used after using the ```destroy_resource_group_contents``` option creates an empty resource group to destroy the resource group previously created.
-
-* The ```destroy_resource_group_contents``` (default: "false") parameter can be used when you want to destroy the resources within a resource group without destroying the resource group itself. For example, the following configuration options used in combination would use an existing resource group (or create one if it doesn't exist) and will destroy the contents of the resource group in the ```kitchen destroy``` phase. If you wish to destroy the empty resource group created after you empty the resource group with this flag you can now set the ```destroy_explicit_resource_group``` to "true" to destroy the empty resource group. 
-
-* The ```destroy_explicit_resource_group_tags``` (default: "true") parameter can be used when you want to remove tags associated with an explicit resource group. The default setting is set to "true" to remain consistent with previous behavior. This should be used in combination with an ```explicit_resource_group_name``` and will be honored during the ```kitchen destroy``` phase.
-
-```yaml
----
-driver:
-  explicit_resource_group_name: stuart-rg-demo-001
-  destroy_explicit_resource_group: false
-  destroy_resource_group_contents: true
-```
-
-* The ```use_ephemeral_osdisk``` (default: false) parameter can be used if you wish to use [ephemeral OS disk functionality](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks).
-
-* The ```secret_url```, ```vault_name```, and ```vault_resource_group``` parameters can be used to deploy VM with specified key vault certificate.
-
-* The ```use_fqdn_hostname``` (default: "false") parameter can be used to determine how kitchen communicates with the Virtual Machine. When true, Kitchen will use the FQDN that is assigned to the Virtual Machine. When false, kitchen will use the public IP address of the machine. This may overcome issues with Corporate firewalls or VPNs blocking Public IP addresses.
-
-## Enabling alternative WinRM configurations
-
-* By default on Windows machines, a PowerShell script runs that enables WinRM over the SSL transport, for Basic, Negotiate and CredSSP connections. To supply your own PowerShell script (e.g. to enable HTTP), use the `winrm_powershell_script` parameter. Windows 2008 R2 example:
-
-```yaml
-platforms:
-  - name: windows2008-r2
-    driver_config:
-      image_urn: MicrosoftWindowsServer:WindowsServer:2008-R2-SP1:latest
-      winrm_powershell_script: |-
-        winrm quickconfig -q
-        winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="512"}'
-        winrm set winrm/config '@{MaxTimeoutms="1800000"}'
-        winrm set winrm/config/service '@{AllowUnencrypted="true"}'
-        winrm set winrm/config/service/auth '@{Basic="true"}'
-
-```
-
 ## Contributing
 
 Contributions to the project are welcome via submitting Pull Requests.
@@ -763,7 +942,7 @@ Stuart Preston
 
 ## License and Copyright
 
-Copyright 2015-2020, Chef Software, Inc.
+Copyright 2015-2021, Chef Software, Inc.
 
 ```
 Licensed under the Apache License, Version 2.0 (the "License");

data/templates/internal.erb

@@ -40,10 +40,9 @@
                 "description": "Unique DNS Name for the Public IP used to access the Virtual Machine."
             }
         },
-        <%- if public_ip_sku %>
         "publicIPSKU": {
             "type": "string",
-            "defaultValue": "Standard",
+            "defaultValue": "Basic",
             "metadata": {
                 "description": "SKU name for the Public IP used to access the Virtual Machine."
             }
@@ -55,7 +54,6 @@
                 "description": "SKU name for the Public IP used to access the Virtual Machine."
             }
         },
-        <%- end %>
         <%- unless os_disk_size_gb.to_s.empty?  -%>
         "osDiskSizeGb": {
             "type": "int",
@@ -261,9 +259,9 @@
             "type": "Microsoft.Network/publicIPAddresses",
             "name": "[variables('publicIPAddressName')]",
             "location": "[variables('location')]",
-	    "sku": {
-	    	"name": "[parameters('publicIPSKU')]"
-	    },
+            "sku": {
+              "name": "[parameters('publicIPSKU')]"
+            },
             "properties": {
                 "publicIPAllocationMethod": "[parameters('publicIPAddressType')]",
                 "dnsSettings": {

data/templates/public.erb

@@ -163,6 +163,20 @@
                 "description": "The nic name created inside of the resource group."
             }
         },
+        "publicIPSKU": {
+            "type": "string",
+            "defaultValue": "Basic",
+            "metadata": {
+                "description": "SKU name for the Public IP used to access the Virtual Machine."
+            }
+        },
+        "publicIPAddressType": {
+            "type": "string",
+            "defaultValue": "Dynamic",
+            "metadata": {
+                "description": "SKU name for the Public IP used to access the Virtual Machine."
+            }
+        },
         "storageAccountType": {
             "type": "string",
             "defaultValue": "<%= storage_account_type %>",
@@ -201,7 +215,6 @@
         "subnetPrefix": "10.0.0.0/24",
         "storageAccountType": "[parameters('storageAccountType')]",
         "publicIPAddressName": "publicip",
-        "publicIPAddressType": "Dynamic",
         "vmStorageAccountContainerName": "vhds",
         "vmName": "[parameters('vmName')]",
         "vmSize": "[parameters('vmSize')]",
@@ -213,7 +226,7 @@
     "resources": [
         {
             "apiVersion": "2017-05-10",
-            "name": "pid-18d63047-6cdf-4f34-beed-62f01fc73fc2", 
+            "name": "pid-18d63047-6cdf-4f34-beed-62f01fc73fc2",
             "type": "Microsoft.Resources/deployments",
             "properties": {
                 "mode": "Incremental",
@@ -241,16 +254,19 @@
         <%- end -%>
         <%- end -%>
         {
-            "apiVersion": "2015-05-01-preview",
+            "apiVersion": "2017-08-01",
             "type": "Microsoft.Network/publicIPAddresses",
             "name": "[variables('publicIPAddressName')]",
             "location": "[variables('location')]",
             "properties": {
-                "publicIPAllocationMethod": "[variables('publicIPAddressType')]",
+                "publicIPAllocationMethod": "[parameters('publicIPAddressType')]",
                 "dnsSettings": {
                     "domainNameLabel": "[parameters('dnsNameForPublicIP')]"
                 }
             },
+            "sku": {
+              "name": "[parameters('publicIPSKU')]"
+            },
             "tags": {
                 <%= vm_tags unless vm_tags.empty? %>
             }
@@ -362,12 +378,12 @@
                     },
                     <%- end -%>
                     <%- if use_ephemeral_osdisk -%>
-                    "osDisk": { 
-                        "diffDiskSettings": { 
-                             "option": "Local" 
-                        }, 
-                        "caching": "ReadOnly", 
-                        "createOption": "FromImage" 
+                    "osDisk": {
+                        "diffDiskSettings": {
+                             "option": "Local"
+                        },
+                        "caching": "ReadOnly",
+                        "createOption": "FromImage"
                     }
                     <%- elsif use_managed_disks -%>
                     "osDisk": {
@@ -408,7 +424,7 @@
                     }
                     <%- end -%>
                     <%- unless data_disks_for_vm_json.nil? -%>
-                      ,"dataDisks": 
+                      ,"dataDisks":
                           <%= data_disks_for_vm_json %>
                     <%- end -%>
                 },

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: kitchen-azurerm
 version: !ruby/object:Gem::Version
-  version: 1.5.2
+  version: 1.5.3
 platform: ruby
 authors:
 - Stuart Preston
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-02-19 00:00:00.000000000 Z
+date: 2021-02-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: azure_mgmt_network