chore(deps): update terraform pagerduty to ~> 3.35.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
pagerduty (source)	required_provider	minor	~> 3.32.0 → ~> 3.35.0
pagerduty (source)	required_provider	minor	~> 3.32.0 → ~> 3.35.0

---

Release Notes

PagerDuty/terraform-provider-pagerduty (pagerduty)

v3.35.0

Compare Source

BREAKING CHANGES

• resource/pagerduty_user_contact_method: user_id is now ForceNew. A contact method's ID is scoped under its user, so changing user_id previously planned an in-place update that always failed with 404 Not Found; it now replaces the resource (1141)

BUG FIXES

• resource/pagerduty_user_contact_method: Honor the caller's error handler when reading back a contact method, so a 404 right after create is retried and then reported instead of being silently treated as "resource gone" and dropped from state (1141)

ENHANCEMENTS

• resource/pagerduty_user_contact_method: Return a clear, actionable error when an update targets a contact method that was deleted outside of Terraform after the plan was generated, pointing at terraform apply -refresh-only instead of surfacing a bare 404 Not Found (1141)

DOCS

• resource/pagerduty_user_contact_method: Document that a contact method deleted in the web interface is re-created by a refresh-enabled plan/apply and does not require terraform state rm (1141)

v3.34.0

Compare Source

ENHANCEMENTS

• resource/pagerduty_service: Return a clear, actionable error when the API rejects deleting the Default Mobilization Service, instead of the raw API error (1133)
• resource/pagerduty_service_integration: Return a clear, actionable error when the API rejects adding an integration to the Default Mobilization Service (1133)
• resource/pagerduty_event_orchestration_path_router: Return a clear, actionable error when the API rejects routing events to the Default Mobilization Service (1133)
• resource/pagerduty_event_orchestration_path_service: Return a clear, actionable error when the API rejects configuring orchestration for the Default Mobilization Service (1133)
• resource/pagerduty_service_dependency: Return a clear, actionable error when the API rejects using the Default Mobilization Service in a service dependency (1133)
• resource/pagerduty_maintenance_window: Return a clear, actionable error when the API rejects targeting the Default Mobilization Service with a maintenance window (1133)

v3.33.1

Compare Source

BUG FIXES

• resource/pagerduty_schedulev2: Preserve the configured teams ordering on refresh so a schedule associated with more than one team no longer shows a perpetual reorder diff (1127)
• resource/pagerduty_schedulev2: Preserve timezone-offset start_time/end_time/effective_until values when they match the API's UTC-normalized return, so applying events with offset timestamps no longer fails with "Provider produced inconsistent result after apply" or shows a perpetual diff (1127)
• resource/pagerduty_schedulev2: Compare effective_since/effective_until semantically when reconciling events, so a timezone-offset/UTC representation change (e.g. after import) no longer triggers a spurious update — which for an active event would needlessly DELETE+CREATE a live shift (1127)

DOCS

• resource/pagerduty_schedulev2: Remove the obsolete flexible-schedules-early-access note, add a legacy-vs-shift-based version mapping table, and add a pagerduty_schedule → pagerduty_schedulev2 migration guide (1127)
• data/pagerduty_schedulev2: Remove the obsolete flexible-schedules-early-access note (1127)

v3.33.0

Compare Source

ENHANCEMENTS

• resource/pagerduty_event_orchestration_path_service: Validate existing config before create to prevent accidental overwrites (1109)
• resource/pagerduty_event_orchestration_path_global: Validate existing config before create to prevent accidental overwrites (1109)
• resource/pagerduty_event_orchestration_path_router: Validate existing config before create to prevent accidental overwrites (1109)
• resource/pagerduty_event_orchestration_path_unrouted: Validate existing config before create to prevent accidental overwrites (1109)

pagerduty/terraform-provider-pagerduty (pagerduty)

v3.35.0

Compare Source

BREAKING CHANGES

• resource/pagerduty_user_contact_method: user_id is now ForceNew. A contact method's ID is scoped under its user, so changing user_id previously planned an in-place update that always failed with 404 Not Found; it now replaces the resource (1141)

BUG FIXES

• resource/pagerduty_user_contact_method: Honor the caller's error handler when reading back a contact method, so a 404 right after create is retried and then reported instead of being silently treated as "resource gone" and dropped from state (1141)

ENHANCEMENTS

• resource/pagerduty_user_contact_method: Return a clear, actionable error when an update targets a contact method that was deleted outside of Terraform after the plan was generated, pointing at terraform apply -refresh-only instead of surfacing a bare 404 Not Found (1141)

DOCS

• resource/pagerduty_user_contact_method: Document that a contact method deleted in the web interface is re-created by a refresh-enabled plan/apply and does not require terraform state rm (1141)

v3.34.0

Compare Source

ENHANCEMENTS

• resource/pagerduty_service: Return a clear, actionable error when the API rejects deleting the Default Mobilization Service, instead of the raw API error (1133)
• resource/pagerduty_service_integration: Return a clear, actionable error when the API rejects adding an integration to the Default Mobilization Service (1133)
• resource/pagerduty_event_orchestration_path_router: Return a clear, actionable error when the API rejects routing events to the Default Mobilization Service (1133)
• resource/pagerduty_event_orchestration_path_service: Return a clear, actionable error when the API rejects configuring orchestration for the Default Mobilization Service (1133)
• resource/pagerduty_service_dependency: Return a clear, actionable error when the API rejects using the Default Mobilization Service in a service dependency (1133)
• resource/pagerduty_maintenance_window: Return a clear, actionable error when the API rejects targeting the Default Mobilization Service with a maintenance window (1133)

v3.33.1

Compare Source

BUG FIXES

• resource/pagerduty_schedulev2: Preserve the configured teams ordering on refresh so a schedule associated with more than one team no longer shows a perpetual reorder diff (1127)
• resource/pagerduty_schedulev2: Preserve timezone-offset start_time/end_time/effective_until values when they match the API's UTC-normalized return, so applying events with offset timestamps no longer fails with "Provider produced inconsistent result after apply" or shows a perpetual diff (1127)
• resource/pagerduty_schedulev2: Compare effective_since/effective_until semantically when reconciling events, so a timezone-offset/UTC representation change (e.g. after import) no longer triggers a spurious update — which for an active event would needlessly DELETE+CREATE a live shift (1127)

DOCS

• resource/pagerduty_schedulev2: Remove the obsolete flexible-schedules-early-access note, add a legacy-vs-shift-based version mapping table, and add a pagerduty_schedule → pagerduty_schedulev2 migration guide (1127)
• data/pagerduty_schedulev2: Remove the obsolete flexible-schedules-early-access note (1127)

v3.33.0

Compare Source

ENHANCEMENTS

• resource/pagerduty_event_orchestration_path_service: Validate existing config before create to prevent accidental overwrites (1109)
• resource/pagerduty_event_orchestration_path_global: Validate existing config before create to prevent accidental overwrites (1109)
• resource/pagerduty_event_orchestration_path_router: Validate existing config before create to prevent accidental overwrites (1109)
• resource/pagerduty_event_orchestration_path_unrouted: Validate existing config before create to prevent accidental overwrites (1109)

v3.32.4

Compare Source

BUG FIXES

• resource/pagerduty_schedulev2: Fix #​1123: prevent "inconsistent result after apply" when modifying shift-defining fields of an active event (1124)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.