add functionality for new attributes in new_service_plan (#48)

Author: donovm4

README.md

@@ -990,8 +990,7 @@ Default: `{}`
 
 ### <a name="input_new_service_plan"></a> [new\_service\_plan](#input\_new\_service\_plan)
 
-Description:   
-  A map of objects that represent a new App Service Plan to create for the Function App.
+Description:   A map of objects that represent a new App Service Plan to create for the Function App.
 
   - `name` - (Optional) The name of the App Service Plan.
   - `resource_group_name` - (Optional) The name of the resource group to deploy the App Service Plan in.
@@ -1004,10 +1003,6 @@ Description:
   - `zone_balancing_enabled` - (Optional) Should zone balancing be enabled for the App Service Plan? Changing this forces a new resource to be created.
   > **NOTE:** If this setting is set to `true` and the `worker_count` value is specified, it should be set to a multiple of the number of availability zones in the region. Please see the Azure documentation for the number of Availability Zones in your region.
 
-  ```terraform
-
-```terraform
-
 Type:
 
 ```hcl

main.service_plan.tf

@@ -1,15 +1,15 @@
 resource "azurerm_service_plan" "this" {
   count = var.create_service_plan ? 1 : 0
 
-  location                   = coalesce(var.new_service_plan.location, var.location)
-  name                       = coalesce(var.new_service_plan.name, "${var.name}-asp")
-  os_type                    = var.os_type
-  resource_group_name        = coalesce(var.new_service_plan.resource_group_name, var.resource_group_name)
-  sku_name                   = var.new_service_plan.sku_name
-  app_service_environment_id = var.new_service_plan.app_service_environment_resource_id
-  tags                       = var.tags
-  # maximum_elastic_worker_count = var.new_service_plan.maximum_elastic_worker_count
-  # worker_count = var.new_service_plan.worker_count
-  # per_site_scaling_enabled = var.new_service_plan.per_site_scaling_enabled
-  zone_balancing_enabled = var.new_service_plan.zone_balancing_enabled
+  location                     = coalesce(var.new_service_plan.location, var.location)
+  name                         = coalesce(var.new_service_plan.name, "${var.name}-asp")
+  os_type                      = var.os_type
+  resource_group_name          = coalesce(var.new_service_plan.resource_group_name, var.resource_group_name)
+  sku_name                     = var.new_service_plan.sku_name
+  app_service_environment_id   = var.new_service_plan.app_service_environment_resource_id
+  maximum_elastic_worker_count = var.new_service_plan.maximum_elastic_worker_count
+  per_site_scaling_enabled     = var.new_service_plan.per_site_scaling_enabled
+  tags                         = var.tags
+  worker_count                 = var.new_service_plan.worker_count
+  zone_balancing_enabled       = var.new_service_plan.zone_balancing_enabled
 }

variables.tf

@@ -907,7 +907,6 @@ variable "new_service_plan" {
 
   }
   description = <<DESCRIPTION
-
   A map of objects that represent a new App Service Plan to create for the Function App.
 
   - `name` - (Optional) The name of the App Service Plan.
@@ -920,11 +919,6 @@ variable "new_service_plan" {
   - `per_site_scaling_enabled` - (Optional) Should per site scaling be enabled for the App Service Plan? Defaults to `false`.
   - `zone_balancing_enabled` - (Optional) Should zone balancing be enabled for the App Service Plan? Changing this forces a new resource to be created.
   > **NOTE:** If this setting is set to `true` and the `worker_count` value is specified, it should be set to a multiple of the number of availability zones in the region. Please see the Azure documentation for the number of Availability Zones in your region.
-
-  ```terraform
-
-  ```terraform
-
   DESCRIPTION
 }