Update Azure Monitor basic logs which now support 30 days instead of 8

[webstean]

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.

Description

On July-25, Microsoft change BASIC table support for a default retention of 30 days, up from 8.

Today, the providers errors, if the retention is set to anything but 8 days, even though if you set it to 8, a review of the console tells you the retention has been set to 30.

resource "azurerm_log_analytics_workspace_table" "basic-sydney" {
  for_each = local.basic_logs_support

  ## the table must exist, otherwise the plan will fail 
  name         = each.key
  workspace_id = azurerm_log_analytics_workspace.shared_log_analytics["sydney"].id
  plan         = "Basic"
  total_retention_in_days = 30 ## does not work
  total_retention_in_days = 8 ## does work

}

New or Affected Resource(s)/Data Source(s)

azurerm_log_analytics_workspace_table

Potential Terraform Configuration

No response

References

https://azure.microsoft.com/en-us/updates/v2/Azure-Monitor-Basic-Logs-Updates

[webstean]

I don't think this PR fully solves the problem:

`retention_in_days` - (Optional) The table's retention in days. Possible values are either `8` (Basic Tier only) or range between `4` and `730`.

That is wrong, 8 should be 30. And, for Basic is cannot be set to anything less than 30 or more than 30.

[github-actions]

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.