Error during terraform apply on existing LA workspace in Free tier

[kamil-makowski]

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 (and AzureRM Provider) Version

azurerm Provider 2.46.1
Terraform 0.14.6

Affected Resource(s)

• azurerm_log_analytics_workspace

Terraform Configuration Files

resource "azurerm_log_analytics_workspace" "shared_hub_loganalytics_we" {
  name                = "${var.prefix}-shr-${var.region_code[var.location_lookup]}-${local.environment}-la"
  location            = var.location[var.location_lookup]
  resource_group_name = data.azurerm_resource_group.internal_hub_rg_we.name
  sku                 = "Free"
  retention_in_days   = 7
  daily_quota_gb      = 0.5
  tags                = var.old_tags
}

Debug Output

Error: `Free` tier SKU quota is not configurable and is hard set to 0.5GB
on main.tf line 41, in resource "azurerm_log_analytics_workspace" "shared_hub_loganalytics_we"

Panic Output

Expected Behaviour

Terraform apply step shouldn't try to change anything on this resource. It already exist in Azure in this configuration but it has been created on older provider version.

Actual Behaviour

During terraform apply step, above error is showing. I have tried to remove daily_quota_gb to stay with default value but behaviour is the same.

Steps to Reproduce

1. terraform apply

Important Factoids

References

• #0000

[chrsundermann]

Any update on this? Error hasn't fixed yet and no workaround seems to exist.

[joshjohanning]

I had this issue occur too after I merely went to go and update the tags on this resource.

Since it didn't house anything yet I just tainted and re-applied, but less than ideal to have to do that for just a tag update.

[katbyte]

@kamil-makowski @chrsundermann @joshjohanning - in this weeks release we will includ a change that might fix this, we sadly can't test as we don't have any historical workspaces to test on. Let us know if this fixes it!

[github-actions]

This functionality has been released in v2.98.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]

This functionality has been released in v3.4.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!

[rcskosir]

Thanks for opening this issue. This was a problem in the 2.x version of the provider which is no longer actively maintained.
If this is still an issue with the 3.x version of the provider please do let us know by opening a new issue, thanks!

[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.