Unclean plan for coralogix_rules_group if order field is used

[vyanchenko-wl]

Summary

With the order field value defined in the terraform code, the plan becomes unclean right after viewing parsing rules in UI.

Affected Resource(s)

• coralogix_rules_group

Terraform Configuration Files

resource "coralogix_rules_group" "serverity-rules" {
  name         = "Severity Rules TF Managed"
  description  = "Extract severity from log message"
  applications = []
  subsystems   = []
  severities   = []
  active       = true
  order        = 100

  rule_subgroups {
    rules {
      extract {
        name               = "Severity Rule"
        description        = "Look for default severity text in log message"
        source_field       = "text"
        regular_expression = "\\b(?P<severity>DEBUG|TRACE|INFO|WARN|WARNING|ERROR|FATAL|EXCEPTION|[Dd]ebug|[Tt]race|[Ii]nfo|[Ww]arn|[Ee]rror|[Ff]atal|[Ee]xception)\\b"
      }
    }
  }
}

Plan Output (no changes in the code was made)

coralogix_rules_group.serverity-rules will be updated in-place

~ resource "coralogix_rules_group" "serverity-rules" {
id = "9f34xxxx-dea8-xxxx-82b7-e173xx423db7"
name = "Severity Rules TF Managed"
~ order = 4 -> 100
# (7 unchanged attributes hidden)

Expected Behavior

Terraform plan shows nothing to change even if you opened /rules UI in Coralogix.

Actual Behavior

With the order field value defined in the terraform code, the plan becomes unclean after viewing parsing rules in UI (no changes!)

Steps to Reproduce

1. terraform apply
2. open parsing rules in Coralogix UI
3. terraform plan - you will get unclean plan

[celaus]

Interesting, thanks for bringing this up. let us check where this comes from.