size_in_tb still expecting 2tb minimum

[bernard-nguyen]

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 comments along the lines of "+1", "me too" or "any updates", 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 and review the contribution guide to help.

Terraform Version

1.6.6

AzureRM Provider Version

3.107.0

Affected Resource(s)/Data Source(s)

azurerm_netapp_pool

Terraform Configuration Files

resource "azurerm_netapp_pool" "example" {
  name                = "example-netapppool"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  account_name        = azurerm_netapp_account.example.name
  service_level       = "Premium"
  size_in_tb          = 1
}

Debug Output/Panic Output

Planning failed. Terraform encountered an error while generating this plan.

Error: expected size_in_tb to be in the range (2 - 500), got 1

Expected Behaviour

Pool with a size of 1TB should be created as this "feature" is in now in GA.

https://azure.microsoft.com/fr-fr/updates/general-availability-azure-netapp-files-support-for-1-tib-capacity-pools/

Actual Behaviour

Error: expected size_in_tb to be in the range (2 - 500), got 1

Steps to Reproduce

1.) Create TF Code
2.) Run TF apply

Important Factoids

No

References

No response

[Dergons]

We also ran into this today when trying to set up a NetApp account

[neil-yechenwei]

Thanks for raising this issue. Azure Doc mentioned that this new feature would be supported since new API version 2024-01-01 but it hasn't been released to Swagger. We will add support for it once this new feature is released to Swagger.

[QBY-ChristianHartmann]

Thanks for merging the fix that the validation accepts 1tb now. Nonetheless the azurerm resource stillt uses the 2023-05-01 API ant therefore the bug persists!

[ldgithub007]

Yes, Plan is passed but apply is still failing even though i am using Azurerm version is 4.5.0. How to change the azurerm to use latest API version 2024-01-01 as mentioned in this Microsoft document? https://learn.microsoft.com/en-us/azure/azure-netapp-files/azure-netapp-files-set-up-capacity-pool
Capacity Pool Name: "pool1"): performing PoolsCreateOrUpdate: unexpected status 400 (400 Bad Request) with error: InvalidValueReceivedFor: An invalid value '1099511627776' was received for Pool.Size. Must be 2 tebibytes in bytes or higher

[ashishchawla-tfc]

Hi team, do we have any update on the same ?

[RickShahid]

Hi, any update on resolving this issue?

The latest Microsoft.NetApp provider API version is 2024-07-01
Here is the Azure CLI command that I use to check for released provider API versions

az provider show --namespace Microsoft.NetApp --query "resourceTypes[?resourceType=='netAppAccounts/capacityPools'].apiVersions[]"