Skip to content
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

Closed
1 task done
niks-singh opened this issue Jul 28, 2022 · 4 comments · Fixed by #17794
Closed
1 task done
Labels
Milestone

Comments

@niks-singh
Copy link

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 "+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

Terraform Version

1.2

AzureRM Provider Version

3.1.15

Affected Resource(s)/Data Source(s)

azurerm_log_analytics_cluster

Terraform Configuration Files

resource "azurerm_log_analytics_cluster" "example" {
  name                = "example-cluster"
  resource_group_name = azurerm_resource_group.example.name
  location            = azurerm_resource_group.example.location

  identity {
    type = "SystemAssigned"
  }
}

Debug Output/Panic Output

Errors out by saying 1000 GB is the minimum supported value. Azure API supports 500 GB minimum size_gb value.

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

@niks-singh niks-singh added the bug label Jul 28, 2022
@github-actions github-actions bot removed the bug label Jul 28, 2022
bubbletroubles added a commit to bubbletroubles/terraform-provider-azurerm that referenced this issue Jul 28, 2022
bubbletroubles added a commit to bubbletroubles/terraform-provider-azurerm that referenced this issue Jul 28, 2022
@bubbletroubles
Copy link
Contributor

I've created PR #17794 to resolve this.

@mybayern1974
Copy link
Collaborator

@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?

@github-actions
Copy link

github-actions bot commented Aug 1, 2022

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!

@github-actions
Copy link

github-actions bot commented Sep 1, 2022

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants