My team is considering managing our SumoLogic enviornment using Terraform and I noticed this issue when importing some existing resources.
Steps to recreate:
- terraform import an existing log search that exists within a subfolder of a larger folder
- change the terraform resource definition to match existing configuration
- apply so that plan shows no difference
- change the parent_id argument to the folder containing the subfolder the search is already contained in
- apply
- the search will still be in the subfolder as shown by terraform plan detailing changes to be made