-
Notifications
You must be signed in to change notification settings - Fork 50
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
sysdig_secure_ml_policy: Using the resource may crash the Terraform process #574
Comments
I am also facing this issue. Thank you! |
Hey @r2bit @dk-teranishis, could you please provide more details on how you're reproducing that? I have built the plugin in your same version, v1.37.2 and so far, I can't replicate it. After deploying it I've triggered plans and applies, and there are no changes on the infrastructure. |
Hi @IgorEulalio The only workaround I've found is to:
This resolves the issue temporarily, but it reoccurs the next day, causing Terraform to fail during plan or apply. Reproduction Steps
Terraform Coderesource "sysdig_secure_aws_ml_policy" "sysdig_runtime_aws_ml" {
name = "Anomalous Console Login Detection"
description = "The Anomalous Console Login Detection feature triggers an event when a login seems unusual compared to normal patterns. Setting a higher confidence level decreases false alarms but may miss actual anomalous logins."
enabled = true
severity = 1
rule {
description = "Test ML Rule Description"
anomalous_console_login {
threshold = 1
enabled = false
}
}
notification_channels = [data.sysdig_secure_notification_channel_slack.critical_notifications.id]
}
Relevant LogsI've attached anonymized logs for reference (trimmed for clarity):
Let me know if you need anything else to help clarify this. |
Use of
sysdig_secure_ml_policy
causes a perpetual diff that cannot be resolved w/o deleting the resource from Terraform state:Once deleted from Sysdig, the plugin crashes:
Terraform code:
The text was updated successfully, but these errors were encountered: