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
Per MS documentation, Storage Shares that belong to Premium storage accounts are allowed quotas up to 100TB, and recently, Standard storage accounts are also allowing quotas up to 100TB (preview). Terraform should not be catching this 5TB limitation before the plan phase.
Actual Behavior
Terraform returns an error before returning a plan:
azurerm_storage_share.testshare: expected quota to be in the range (1 - 5120), got 6144
Steps to Reproduce
Configure code above
Run terraform plan
Important Factoids
References
The text was updated successfully, but these errors were encountered:
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
Sep 10, 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 -- 0.11.13
AzureRM -- 1.32.1
Affected Resource(s)
azurerm_storage_share
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Per MS documentation, Storage Shares that belong to Premium storage accounts are allowed quotas up to 100TB, and recently, Standard storage accounts are also allowing quotas up to 100TB (preview). Terraform should not be catching this 5TB limitation before the
plan
phase.Actual Behavior
Terraform returns an error before returning a plan:
azurerm_storage_share.testshare: expected quota to be in the range (1 - 5120), got 6144
Steps to Reproduce
terraform plan
Important Factoids
References
The text was updated successfully, but these errors were encountered: