Story Summary
As a platform engineer, I want pagerduty_schedule.ghost-stack_dev migrated to pagerduty_schedulev2, so that our PagerDuty schedule continues to function once the legacy v1 API resource is removed from the provider.
✅ Acceptance Criteria
📝 Additional Context
Current deprecation warning from tofu plan:
│ Warning: Deprecated Resource
│
│ with module.pagerduty.pagerduty_schedule.ghost-stack_dev,
│ on ../../modules/pagerduty/main.tofu line 259, in resource "pagerduty_schedule" "ghost-stack_dev":
│ 259: resource "pagerduty_schedule" "ghost-stack_dev" {
│
│ Use pagerduty_schedulev2 instead. pagerduty_schedule uses the legacy v1 API
│ and will be removed in a future release.
📦 Definition of Ready
✅ Definition of Done
Story Summary
As a platform engineer, I want
pagerduty_schedule.ghost-stack_devmigrated topagerduty_schedulev2, so that our PagerDuty schedule continues to function once the legacy v1 API resource is removed from the provider.✅ Acceptance Criteria
opentofu/modules/pagerduty/main.tofuusespagerduty_schedulev2(notpagerduty_schedule) forghost-stack_devtofu state mvormoved {}block — no schedule recreation (would lose history and disrupt on-call)tofu planon develop shows no changes to the schedule after migration (in-place move only)📝 Additional Context
Current deprecation warning from
tofu plan:opentofu/modules/pagerduty/main.tofu:259pagerduty/pagerduty ~> 3.32.0(checkpagerduty_schedulev2schema parity before migrating — attribute names may differ)movedblock so OpenTofu renames the resource in state rather than destroying and recreating it📦 Definition of Ready
✅ Definition of Done