-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rotation_virtual_start constantly trying to change #168
Comments
@yzargari Did you solve this problem? |
It is related to your time_zone setting in terraform. |
@iwasnobody Thanks for sharing your solution! I can update the docs to make this point more clear. Just to make sure I have your solution correct, you're saying that the |
rotation_virtual_start's timezone should be the same as time_zone setting. For example, I set the time_zone be Asia/shanghai, so the rotation_virtual_start need to be set +08:00 resource "pagerduty_schedule" "ivanyu_daytime" { layer {
} |
PR #321 which was merged and included in Going to close the issue. Please repost if that is not the case and we can investigate further. |
Hello,
I've seen my problem reported in #4 and supposedly fixed in #1 over two years ago - but it looks like I'm still having the same issue with TF 0.12.12 and PD provider 1.3.1.
Essentially the problem is most likely related to having my account set with timezone of UTC+2 and my TF manifest is set by UTC. Terraform therefore thinks there's difference between what's set and what's need to be set and wants to change it - whereas, the "different" times are actually the same.
For example:
If I say yes to this, it will seemingly show a successful change:
pagerduty_schedule.schedule_daytime[0]: Modifying... [id=XXXXXXX]
pagerduty_schedule.schedule_daytime[0]: Modifications complete after 1s [id=XXXXXXX]
But then if I run terraform again, it will show the same modification to make:
Thanks,
Joseph
The text was updated successfully, but these errors were encountered: