Managing PagerDuty schedules with Terraform leads to conflicts due to manual overrides

[sanusatyadarshi]

Terraform Version

terraform -v

Terraform version: v0.13 PagerDuty provider version: v3.15.6(not defined in providers)

Affected Resource(s)

pagerduty_schedule

Terraform Configuration Files

resource "pagerduty_schedule" "example" {
  name        = "Example On-call Schedule"
  time_zone   = "UTC"
  users       = ["user1@example.com", "user2@example.com"]
  start       = "2024-09-15T09:00:00Z"
  end         = "2024-09-15T17:00:00Z"
}

Debug Output

N/A

Panic Output

N/A

Panic Output

Terraform should allow for ongoing management of PagerDuty schedules without conflicts from manual updates made through the UI.

Actual Behavior

Manual changes made to schedules in the PagerDuty UI are overwritten when applying updates through Terraform, causing conflicts and disrupting schedule management.

Steps to Reproduce

1. Create a PagerDuty schedule using Terraform.
2. Manually change the schedule via the PagerDuty UI.
3. Add or update team members in the Terraform configuration.
4. Apply the Terraform configuration.
5. Observe that the manual changes are overwritten.

Important Facts:

We are aiming for full management of PagerDuty schedules using Infrastructure as Code (IAC) and do not want to manage schedules manually via the PagerDuty UI. The recommended approach of manual overrides conflicts with this goal and leads to potential inconsistencies.

References

None at this time.