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_log_search does not move existing log search in proper folder #715

Open
pdobrzanski-appfire opened this issue Jan 14, 2025 · 1 comment

Comments

@pdobrzanski-appfire
Copy link

pdobrzanski-appfire commented Jan 14, 2025

Hello,

I am moving existing dashboards and queries into SumoLogic Library (not a personal folder).

For folder it works ok like this

resource "sumologic_dashboard" "main" {
  folder_id = "00000000052FB492"
  ...
  }

However, for log search like:

  name = "Some name"
  description = "Some description"
  parent_id = "000000000532E867"

terraform shows plan properly and executes ok.

        id                  = "000000000537CD2C"
        name                = "Some name"
      ~ parent_id           = "0000000003F43AB9" -> "000000000532E867"
        # (4 unchanged attributes hidden)

        # (2 unchanged blocks hidden)
    }

Unfortunately, there is no change in SL and plan shows the difference again.
I thought this might be permission issue - but copying existing into folder worked ok.

When those existing log queries were removed (comment out and terraform apply) and recreated - they were put in correct folder.
So looks like problem is only with update.

Terraform v1.9.5
sumologic/sumologic v2.31.5

@pdobrzanski-appfire
Copy link
Author

Actually looks like duplicate of #700

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

1 participant