Running a plan on a quality gate identifies changes, when in fact there a none

[mpas]

Terraform Version

1.9.8

Provider Version

0.16.14

Affected Resource(s)

Please list the resources as a list, for example:

• sonarqube_qualitygate

Terraform Configuration Files

resource "sonarqube_qualitygate" "sonar_way_with_line_coverage" {
  name       = "SonarWay (C++/GCov Tuned Gate)"
  is_default = false

  condition {
    metric    = "new_technical_debt"
    op        = "GT"
    threshold = "5"
  }

  condition {
    metric    = "new_blocker_violations"
    op        = "GT"
    threshold = "0"
  }
}

Expected Behavior

As the gate is deployed I should not expect changes, when running a terraform plan. For a plan with a single condition this works but when I add a second condition I constantly see changes when a new plan is executed. The conditions seems to swapped (see picture)

Actual Behavior

What actually happened?
The gate has been deployed, but after a second run, for example a plan the conditions are mixed up

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply
2. terraform plan (expect no changes)

I’m experiencing the same issue. For some reason, the condition’s ID remains unchanged, while all the other attributes are updated.

[Sam13]

Same problem here.
I was able to workaround this by sorting all conditions according their metric name when creating the resource.
Plan does not show any diffs.
Diff is still not nice when adding new conditions but seems to work as well.

Probably caused by this:

terraform-provider-sonarqube/sonarqube/resource_sonarqube_qualitygate.go

Line 369 in bed4dd1

// Make sure the order is always the same for when we are comparing lists of conditions

Thank you for sharing this workaround. Sorting the conditions by metric name worked perfectly for me too. Really appreciate it!