Issue with pagerduty_schedule and rotation_virtual_start

[hashibot]

This issue was originally opened by @michaelcurran as hashicorp/terraform#11424. It was migrated here as part of the provider split. The original body of the issue is below.

---

Hi there,

I am trying to use pagerduty_schedule to set a weekly rotation and rotation_virtual_start to set a specific handoff time within the schedule.

Terraform Version

Terraform v0.8.4

Affected Resource(s)

• pagerduty_schedule

Terraform Configuration Files

resource "pagerduty_schedule" "something" {
  name      = "something"
  time_zone = "America/New_York"

  layer {
    name                         = "Layer 1"
    start                        = "2017-01-20T04:00:00-05:00"
    rotation_virtual_start       = "2017-01-20T16:00:00-05:00"
    rotation_turn_length_seconds = 604800

    users = [
      "${data.pagerduty_user.some_user.id}",
    ]
  }
}

Expected Behavior

Using rotation_virtual_start you should be able to adjust the schedule handoff time, and it should remain set to the specified time.

Actual Behavior

Once rotation_virtual_start has been set future changes to it are not detected during plans, and additional changes to the pagerduty_schedule resource, such as adding or removing users, cause the handoff time to change even though rotation_virtual_start has not been updated. I've noticed the change seems to decrease by 5 hours on each apply.

Steps to Reproduce

For rotation_virtual_start changes not being detected:

1. Create a pagerduty_schedule resource
2. terraform apply
3. Update rotation_virtual_start
4. terraform plan

For the handoff time being updated when not updating rotation_virtual_start:

1. Create a pagerduty_schedule resource
2. terraform apply
3. Check the schedule in PagerDuty
4. Add a user to the pagerduty_schedule resource (or add it directly within PagerDuty)
5. terraform apply (the handoff time for the schedule in PagerDuty should have changed)

[heimweh]

Closing this since this should be resolved with the changes in #1.