-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log analytics cluster supports minimum 1000 GB Size/day but Azure supports 500 GB minimum #17787
Comments
I've created PR #17794 to resolve this. |
@bubbletroubles thank you for opening this issue and further appreciate to submit a PR! Given there is an existing PR #17780 that not only tries to resolve this issue but includes some more info, would you mind subscribing that PR? |
This functionality has been released in v3.16.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Is there an existing issue for this?
Community Note
Terraform Version
1.2
AzureRM Provider Version
3.1.15
Affected Resource(s)/Data Source(s)
azurerm_log_analytics_cluster
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Actual Behaviour
Error when passing 500 GB as Size_GB parameter
Steps to Reproduce
No response
Important Factoids
No response
References
https://docs.microsoft.com/en-us/azure/azure-monitor/logs/logs-dedicated-clusters#create-a-dedicated-cluster refer the link
The text was updated successfully, but these errors were encountered: