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

azurerm_monitor_alert_processing_rule_suppression missing monitor_condition in atLeastOneOf #19318

Closed
1 task done
bloewes opened this issue Nov 16, 2022 · 2 comments · Fixed by #19338
Closed
1 task done

Comments

@bloewes
Copy link
Contributor

bloewes commented Nov 16, 2022

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

AzureRM Provider Version

3.31.0

Affected Resource(s)/Data Source(s)

azurerm_monitor_alert_processing_rule_suppression

Terraform Configuration Files

resource "azurerm_monitor_alert_processing_rule_suppression" "adf_infra" {
  name                = "foo"
  resource_group_name = "bar"
  scopes              = [scope.id]

  condition {
    monitor_condition {
      operator = "Equals"
      values   = ["Resolved"]
    }
  }
}

Debug Output/Panic Output

╷
│ Error: Missing required argument
│ 
│   with module.foo,
│   on modules/file.tf line 153, in resource "azurerm_monitor_alert_processing_rule_suppression" "adf_infra":
│  153:   condition {
│ 
│ "condition.0.target_resource": one of
│ `condition.0.alert_context,condition.0.alert_rule_id,condition.0.alert_rule_name,condition.0.description,condition.0.monitor_service,condition.0.severity,condition.0.signal_type,condition.0.target_resource,condition.0.target_resource_group,condition.0.target_resource_type`
│ must be specified

Expected Behaviour

Specifying condition monitor_condition should be enough.
I need to e.g. add severity block
severity {
operator = "Equals"
values = ["Sev1"]
}

for the error to disappear.

See

"alert_context": schemaAlertProcessingRuleCondition(
alertprocessingrules.PossibleValuesForOperator(), nil,
[]string{"condition.0.alert_context", "condition.0.alert_rule_id", "condition.0.alert_rule_name",
"condition.0.description", "condition.0.monitor_service", "condition.0.severity", "condition.0.signal_type",
"condition.0.target_resource", "condition.0.target_resource_group", "condition.0.target_resource_type"},

monitor_condition entry is missing for this entry and the other ones also.

Actual Behaviour

See Output

Steps to Reproduce

terraform plan

Important Factoids

No response

References

No response

@github-actions
Copy link

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

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 Dec 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.