You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The resource should have accepted the SKU Name of StandardPool as a valid SKU Name and created the pool.
Actual Behavior
Using the value 'StandardPool' generates the folling error:
azurerm_mssql_elasticpool.pool: sql.ElasticPoolsClient#CreateOrUpdate: Failure sending request: StatusCode=0 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidSkuName" Message="Invalid SKU name 'StandardPool'."
Attempting to use a different value such as Standard returns a list of acceptable values including StandardPool:
Error: module.sqlserver.azurerm_mssql_elasticpool.pool: expected sku.0.name to be one of [BasicPool StandardPool PremiumPool GP_Gen4 GP_Gen5 BC_Gen4 BC_Gen5], got Standard
Steps to Reproduce
Create terraform code using the value StandardPool for the Sku Name parameter on the azurerm_mssql_elasticpool resource.
terraform apply
#0000
The text was updated successfully, but these errors were encountered:
@ktobin-occm Thanks for opening this issue. This can be terribly confusing, the new API merges support for DTU and vCore based ElasticPool SKUs into a single API. The current way you have your SKU defined you have the name set for a DTU based SKU and the tier for a vCore based SKU which is not valid and why you are seeing the error you are getting. The correct configuration for a StandardPoolSKU would be:
@ktobin-occm with my new PR if you attempted to use your sample configuration file you would now get the below error, which I feel is easier to understand and points out what the issue is with the file.
Error: Error running plan: 1 error(s) occurred:
* azurerm_mssql_elasticpool.test: 1 error(s) occurred:
* azurerm_mssql_elasticpool.test: Mismatch between SKU name 'StandardPool' and tier 'GeneralPurpose', expected 'tier' to be 'Standard'
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!
ghost
locked and limited conversation to collaborators
Mar 7, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform (and AzureRM Provider) Version
'Terraform v0.11.11
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The resource should have accepted the SKU Name of
StandardPool
as a valid SKU Name and created the pool.Actual Behavior
Using the value 'StandardPool' generates the folling error:
Attempting to use a different value such as
Standard
returns a list of acceptable values includingStandardPool
:Steps to Reproduce
Create terraform code using the value
StandardPool
for the Sku Name parameter on the azurerm_mssql_elasticpool resource.terraform apply
The text was updated successfully, but these errors were encountered: