Cannot create Azure NetApp volumes larger then 4TB.

[a0099953]

getting the following error when trying to create an Azure Netapp Volume larger then 4tb:

2020-01-21T13:06:21.4006057Z Acquiring state lock. This may take a few moments...
2020-01-21T13:06:22.6628508Z [31m
2020-01-21T13:06:22.6630324Z [1m[31mError: [0m[0m[1mexpected storage_quota_in_gb to be in the range (100 - 4096), got 16896[0m
2020-01-21T13:06:22.6630651Z
2020-01-21T13:06:22.6631197Z [0m on modules/netapp/main.tf line 11, in resource "azurerm_netapp_volume" "hanadata":
2020-01-21T13:06:22.6631739Z 11: resource "azurerm_netapp_volume" "hanadata" [4m{[0m
2020-01-21T13:06:22.6632244Z [0m
2020-01-21T13:06:22.6632687Z [0m[0m
2020-01-21T13:06:22.8716358Z ##[error]Error: The process '/home/saplocadmin/myagent/_work/_tool/terraform/0.12.19/x64/terraform' failed with exit code 1

[katbyte]

This should be fixed by #5485

[paulomarquesc]

@a0099953, the PR #5485 carrying the fix was merged yesterday.

[Bungleboy]

From what I can tell this wasn't completely fixed with #5485. The resource_arm_netapp_volume.go file still had this in the validation (as of release 2.2.0)
"storage_quota_in_gb": { Type: schema.TypeInt, Required: true, ValidateFunc: validation.IntBetween(100, 4096),
This is still causing the same error to appear. I've noticed though the value has increased in the master branch. Presumably someone has fixed this and added it to the next release. Commenting here in case others are still having the issue.

[paulomarquesc]

This is now fixed and already published on v2.3 of the provider. #6228

[tombuildsstuff]

Fixed via #6228 - thanks @paulomarquesc

[ghost]

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!