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

Setting parent_id doesn't move existing log searches #700

Open
gray-host opened this issue Oct 25, 2024 · 1 comment
Open

Setting parent_id doesn't move existing log searches #700

gray-host opened this issue Oct 25, 2024 · 1 comment
Labels

Comments

@gray-host
Copy link

My team is considering managing our SumoLogic enviornment using Terraform and I noticed this issue when importing some existing resources.

Steps to recreate:

  1. terraform import an existing log search that exists within a subfolder of a larger folder
  2. change the terraform resource definition to match existing configuration
  3. apply so that plan shows no difference
  4. change the parent_id argument to the folder containing the subfolder the search is already contained in
  5. apply
  6. the search will still be in the subfolder as shown by terraform plan detailing changes to be made
@dlinsumo
Copy link
Collaborator

Internal tracking ticket SUMO-250025

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

No branches or pull requests

2 participants