Skip to content

Setting parent_id doesn't move existing log searches #700

@gray-host

Description

@gray-host

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions