Need ability to configure the "performance tier" for azurerm_managed_disk

[fcatacut]

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

Description

For certain storage types other than Standard_LRS, a "performance tier" option is available in Azure Porta which can be set to a higher performance tier to meet higher demand and return to the initial baseline performance tier once this period is complete.

This is not currently supported in the azurerm_managed_disk resource.

New or Affected Resource(s)

• azurerm_managed_disk

Potential Terraform Configuration

resource "azurerm_managed_disk" "source" {
  name                 = "data"
  location             = "centralus"
  resource_group_name  = azurerm_resource_group.example.name
  storage_account_type = "Premium_LRS"
  create_option        = "Empty"
  disk_size_gb         = "64"
  tier                 = "P6" # New argument
}

References

ARM Template snippet

"properties": {
    "creationData": {
        "createOption": "Empty"
    },
    "diskSizeGB": 64,
    "diskIOPSReadWrite": 500,
    "diskMBpsReadWrite": 100,
    "encryption": {
        "type": "EncryptionAtRestWithPlatformKey"
    },
    "diskState": "Attached",
    "networkAccessPolicy": "AllowAll",
    "tier": "P10"
}

[aristosvo]

Gave it a shot and included some extra configuration around only enabling the option only for Premium SSDs + acceptance tests! 🎉

[ghost]

This has been released in version 2.59.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.59.0"
}
# ... other configuration ...

[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.