Closed steve-hawkins closed 5 years ago
@steve-hawkins thank you for reporting this issue, however this is not a supported scenario all resources need to be either vCore based or DTU based. That said using the files you supplied above, I did get this to work by switching the elasticpool to a StandardPool
like this:
resource "azurerm_mssql_elasticpool" "example" {
name = "example-repro-elasticpool"
resource_group_name = "${azurerm_resource_group.example.name}"
location = "${azurerm_resource_group.example.location}"
server_name = "${azurerm_sql_server.example.name}"
sku {
name = "StandardPool"
capacity = 100
tier = "Standard"
}
per_database_settings {
min_capacity = 0
max_capacity = 100
}
}
I also noticed a typo in the original files...
From this:
elastic_pool_name = "${azurerm_sql_server.example.name}"
To this:
elastic_pool_name = "${azurerm_mssql_elasticpool.example.name}"
Hope this helps.
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!
Community Note
Terraform (and AzureRM Provider) Version
Affected Resource(s)
Terraform Configuration Files
Start with the following:-
Then try to change to the following:-
Debug Output
N/A
Panic Output
N/A
Expected Behavior
Migrate from individually managed DTU based databases to vCore based elastic pool
Actual Behavior
Steps to Reproduce
terraform apply
first set of config mentioned aboveterraform apply
second set of config mentioned aboveImportant Factoids
References
590
2369