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

bug: lacework_alert_rule without subcategories yields an error on apply #597

Open
danthegoodman opened this issue Nov 29, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@danthegoodman
Copy link

Describe the bug
I tried to create a lacework_alert_rule without subcategories. I got an error. I was able to create it online and import it with no changes just fine.

To Reproduce

resource "lacework_alert_rule" "slack" {
  name           = "Slack"
  alert_channels = [local.slack_channel_id]
  severities     = ["Critical", "High"]
  description    = "Send all Crit and High alarms to Slack"
}

Expected behavior
The alert rule to be created correctly.

Screenshots

lacework_alert_rule.slack: Creating...
│ Error: 
│   [POST] https://outschool.lacework.net/api/v2/AlertRules
│   [400] Invalid data: #1: [filters/subcategory: instance type (null) does not match any allowed primitive type (allowed: ["array"])] 
│ 
│   with lacework_alert_rule.slack,
│   on alert-rules.tf line 6, in resource "lacework_alert_rule" "slack":
│    6: resource "lacework_alert_rule" "slack" {
│ 

Please complete the following information):

  • OS: registry.gitlab.com/gitlab-org/terraform-images/releases/1.4:v1.0.0
  • Provider Version: 1.17.0

Additional context
Add any other context about the problem here.

@danthegoodman danthegoodman added the bug Something isn't working label Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant