pagerduty_event_orchestration_service rule label not persistant (diff in every plan)

[martinpiegay]

Hi,
The label label within the rule argument of the pagerduty_event_orchestration_service resource consistently shows as a diff, even when no actual changes are made. This behavior is observed from one Terraform plan/apply to another.

Terraform Version

1.8.1

Affected Resource(s)

• pagerduty_event_orchestration_service (label param)

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

resource "pagerduty_event_orchestration_service" "www" {
  service = pagerduty_service.example.id
  enable_event_orchestration_for_service = true
  set {
    id = "start"
    rule {
      label = "All critical alerts should be treated as P1 incident"
      condition {
        expression = "event.severity matches 'critical'"
      }
      actions {
        annotate = "Please use our P1 runbook: https://docs.test/p1-runbook"
        priority = data.pagerduty_priority.p1.id
        incident_custom_field_update {
          id = pagerduty_incident_custom_field.cs_impact.id
          value = "High Impact"
        }
      }
    }

Expected Behavior

After the initial Terraform apply, the label field should not appear in the diff output if no changes are made to its value.

Actual Behavior

Terraform plan/apply consistently shows a diff for the label field, even when its value remains the same

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
! update in-place

Terraform will perform the following actions:

  # pagerduty_event_orchestration_service.www will be updated in-place
! resource "pagerduty_event_orchestration_service" "www" {
        id                                     = "***"
        # (2 unchanged attributes hidden)

!       set {
            id = "start"

!           rule {
                id       = "e38ca319"
-               label    = "Please use our P1 runbook: https://docs.test/p1-runbook" -> null

                # (2 unchanged blocks hidden)
            }
        }

    }

Plan: 0 to add, 1 to change, 0 to destroy.

Steps to Reproduce

1. Apply the provided Terraform configuration.
2. Run terraform plan again without making any changes to the label value.
3. Observe the diff output and notice the change in the label field.

Important Factoids

NA

References

NA