Request to support the Azure SQL Hyperscale Service Tier Premium Series Hardware SKU

[willholtkamp]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

1.4.2

AzureRM Provider Version

3.60

Affected Resource(s)/Data Source(s)

azurerm_mssql_database

Terraform Configuration Files

terraform {
  required_providers {
    azurerm = {
      source = "hashicorp/azurerm"
      version = "~> 3.60"
    }
  }
}

provider "azurerm" {
  features {}
}

data "azurerm_client_config" "current" {}

resource "azurerm_resource_group" "database" {
  name     = "my-resource-group"
  location = "eastus"
}

resource "azurerm_mssql_server" "database" {
  name                         = "my_server_name"
  resource_group_name          = azurerm_resource_group.database.name
  location                     = azurerm_resource_group.database.location
  version                      = "12.0"
}

resource "azurerm_mssql_database" "database" {
  name                           = "my_database_name"
  server_id                      = azurerm_mssql_server.database.id
  sku_name                       = "HS_PRMS_18"
}

Debug Output/Panic Output

Error: invalid value for sku_name (This is not a valid sku name. For example, a valid sku name is 'GP_S_Gen5_1','HS_Gen4_1','BC_Gen5_2', 'ElasticPool', 'Basic', 'S0', 'P1'.)

Expected Behaviour

For Azure SQL Database, Microsoft has a "Premium Series" Hardware configuration for the Hyperscale tier (not to be confused with the normal Premium Service tier). It appears the SKU name validation only support GEN4, GEN5, and serverless for the Hyperscale tier.

I'm not sure what would be the best way to implement this? A new constant or an update to an existing constant in the SKU validator here. Either way, I believe the AzureRM should support this option.

Actual Behaviour

Cannot provision the Premium Series hardware configuration for the Hyperscale Service Tier

Steps to Reproduce

1. terraform init
2. terraform plan

Important Factoids

No response

References

No response

[github-actions]

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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.