You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any on-call schedule entries that pass the date range bounds will be truncated at the bounds, unless the parameter overflow=true is passed. This parameter defaults to false. For instance, if your schedule is a rotation that changes daily at midnight UTC, and your date range is from 2011-06-01T10:00:00Z to 2011-06-01T14:00:00Z:
If you don't pass the overflow=true parameter, you will get one schedule entry returned with a start of 2011-06-01T10:00:00Z and end of 2011-06-01T14:00:00Z.
If you do pass the overflow=true parameter, you will get one schedule entry returned with a start of 2011-06-01T00:00:00Z and end of 2011-06-02T00:00:00Z.
Actual Behavior
Schedule changed after every terraform apply command gets run
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Create a schedule
Have list of users in the order they should be on-call
Run terraform apply
Login into PD, see the schedule got shifted (updated)
5 Run terraform apply again
Important Factoids
From PD documentation
The text was updated successfully, but these errors were encountered:
Hi Guys( @radeksimko@heimweh), is it possible to merge this fix to prod? , we are very much dependent on it and has been waiting for a couple of months. Thank you a lot!
Hi there,
Terraform Version
terraform_0.9.8
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Would expect schedule didn't change since it was set once
To fix this issue the flag
overflow=true
needs to be passed. according to the PD doc https://v2.developer.pagerduty.com/v2/page/api-reference#!/Schedules/put_schedules_idActual Behavior
Schedule changed after every
terraform apply
command gets runSteps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform apply
5 Run
terraform apply
againImportant Factoids
From PD documentation
The text was updated successfully, but these errors were encountered: