App Service Plan: support for attaching to an App Service Environment

[tombuildsstuff]

Unfortunately as we don't support creating App Service Environments in Terraform yet (they take 1.5-2 hours to provision) - I can't add a test for this behaviour at the current time..

I've got a branch with some initial scaffolding for App Service Environments, but testing it is kind of painful - but I'd hope that we should be able to add support for this in the near future, when we do - I'll be sure to add some tests for this retroactively

[mbfrahry]

LGTM

[tombuildsstuff]

Manual confirmation that attaching to a V1 App Service Environment works ✅

[tombuildsstuff]

App Service Plan Resource tests pass:

App Service Plan Data Source tests pass:

$ acctests azurerm TestAccDataSourceAzureRMAppServicePlan_
=== RUN   TestAccDataSourceAzureRMAppServicePlan_basic
--- PASS: TestAccDataSourceAzureRMAppServicePlan_basic (89.57s)
=== RUN   TestAccDataSourceAzureRMAppServicePlan_complete
--- PASS: TestAccDataSourceAzureRMAppServicePlan_complete (65.87s)
PASS
ok  	github.com/terraform-providers/terraform-provider-azurerm/azurerm	155.471s

[tombuildsstuff]

Fixes #712

[davidlbyrne]

I have started to create IaC with terraform and we have been hung up on the Azure ASE integration.

When I don't specify the key for maximum_number_of_workers I get this error:
azurerm_app_service_plan.ilbase-plan:
Status=400 Code="BadRequest" Message="NumberOfWorkers is invalid."

When I add it into the properties block:
azurerm_app_service_plan.ilbase-plan: properties.0: invalid or unknown key: maximum_number_of_workers

Maybe I don't understand how this is supposed to work. Any help would be greatly appreciated.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!