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

sumologic_monitor resource does not support sumologic_folder resources as parent_id #676

Open
kcarrillorhoads opened this issue Jul 26, 2024 · 1 comment

Comments

@kcarrillorhoads
Copy link

When defining sumologic_monitor entities even if the sumologic_folder resource is in the same state, the monitor will fail creation if the parent_id is set to a sumologic_folder:

parent_id= sumologic_folder.security_monitors.id

│ Error: {"id":"HXYMD-VNQXH-WHANG","errors":[{"code":"content:parent_not_found","message":"Parent object not found."}]}

│ with module.team-specific.module.security.sumologic_monitor.guardduty_high_severity_threats,
│ on modules/sumo-team-specific/security/guardduty.tf line 240, in resource "sumologic_monitor" "guardduty_high_severity_threats":
│ 240: resource "sumologic_monitor" "guardduty_high_severity_threats" {

@kevin-sumo
Copy link
Collaborator

Monitors have a distinct folder structure and are managed via a separate sumologic_monitor_folder resource. So you'll need to create a folder using this resource, then point your monitors to the parent ID of that folder.

The folders resource is currently only for managing the folders found within the Content Library.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants