@bijection/connectors/pagerduty entrypoint to declare PagerDuty resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
Incidents
roster: Open-incident roster and acceptance-only Events v2 sends
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:pagerduty/incidents/roster/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: pagerduty. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Configuration: acknowledged
Case:pagerduty/incidents/roster/acknowledged.
Connection and resource configuration are declared by this exact case.
Credential kind: pagerduty. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Compiled declaration examples and configuration details are published in the connector reference. The connection’s default role readshttps://api.pagerduty.com with a
pagerduty credential written Authorization: Token token=<key> (a keyword
credential). PagerDuty exposes no account identity to an account key, so a
binding names one service (serviceId) that the key must be able to read; that
service id is the connection’s identity and the roster is that service’s.
incidents.roster reads one page of up to 100 of the service’s incidents in one
status (triggered by default, or acknowledged). PagerDuty pages by offset over
a changing list, which can skip or repeat rows, and states no cursor, so a
computed offset is not followed and a larger roster is read partially. An
incident leaving the roster is not withdrawn; point reconciliation reads it again
and publishes its current status, such as resolved.
send posts one Events v2 event (trigger, acknowledge or resolve with a
dedup_key) to events.pagerduty.com under the connection’s events credential
role, whose routing key the host places in the body. Events v2 answered 202 for a
routing key naming no integration and for a disabled service, so a 202 is
accepted delivery of a well-formed event and establishes no incident. A
plain-text 400 is a shape refusal. No incident record is created by a send;
reconciliation of an unknown send stays unknown because a later incident lookup
cannot say which send produced it.
Nothing here has run against PagerDuty or been qualified.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.