pagerduty: add 2 doc-sourced samples - #60
Merged
Merged
Conversation
incident.priority_updated and service.updated, the two complete V3 webhook deliveries published on PagerDuty's webhooks-overview page. Exported from the webhook-registry harvest (hookdeck/webhook-registry#82). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New provider: PagerDuty V3 webhook subscriptions. These are the last stage of the add-a-source pipeline after the skill (hookdeck/webhook-skills#210), the core source type (hookdeck/core#5772), the registry row (hookdeck/webhook-registry#82) and the check record (hookdeck/webhook-registry-checks#14).
.mdmirror), verbatim:incident.priority_updatedandservice.updated.event.dataobjects, not deliveries, and wrapping one in an envelope would inventevent.id,occurred_at,agentandclientvalues. Also excluded ispagey.ping, the test delivery from the ping endpoint: no body is published, and it is not in the Event Types table.content-typeonly. The signature (X-PagerDuty-Signature) and the dedup id (X-Webhook-Id) are per-delivery values a doc can't supply, and the topic is carried in the body, so there's no topic header.topic_identifier:event.event_type. The body is{"event": {...}}with no top-level type. Per SAMPLE-PUBLISHING rule 6 it's kept dotted and not flattened:requestReceiver.tswon't resolve it, but every file carries an explicittopic.latest. PagerDuty stamps no payload version ("V3" names the subscription generation), and there was no existing entry to adopt.latestis markedsourced_via: docs,sourced_on: 2026-10-02. Each file carriessource.type: vendor-documentation.Checklist:
providers/pagerdutyand noscripts/pagerdutyharness, so no captures are displaced. Existing files changed: 0.samples-doc/.yarn compilepasses: 146 → 147 providers, no topic collisions.yarn test: 14/14 passed.verify.py: FAIL (0).Evidence and non-assertions are in hookdeck/webhook-registry#82.
🤖 Generated with Claude Code