Support for alert_rule_template_version in the azurerm_sentinel_alert_rule_scheduled resource

[Korving-F]

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

Description

Currently there is a missing field which can help indicate updates to template-based rules. Adding an alert_rule_template_version field would solve that. This relates to the existing alert_rule_template_guid field.

New or Affected Resource(s)

• azurerm_sentinel_alert_rule_scheduled

Potential Terraform Configuration

resource "azurerm_sentinel_alert_rule_scheduled" "example" {
  name                       = "example"
  log_analytics_workspace_id = azurerm_log_analytics_solution.example.workspace_resource_id
  display_name               = "example"
  severity                   = "High"
  alert_rule_template_guid = aaaa-bbbb-cccc-dddd
  alert_rule_template_version = 1.0.0
  query                      = <<QUERY
AzureActivity |
  take 10
QUERY
}

References

• azurerm_sentinel_alert_rule_scheduled - support alert_rule_template_guid #9712

[magodo]

@Korving-F After looking through the Swagger spec of the sentinel alert rule, there seems no such property for template version, would you please confirm?

[Korving-F]

@magodo One can see it defined in 2021-09-01-preview as templateVersion under QueryBasedAlertRuleProperties.
Thanks for the follow up! ^_^

[github-actions]

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

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.