imbi-plugin-pagerduty
The PagerDuty plugin for the Imbi
platform, distributed as a single Python package (imbi_plugin_pagerduty)
exposing one Integration (pagerduty) with four capabilities:
lifecycle— provisions and maintains a PagerDuty service for each project, routed to the owning team's escalation policy (via theteam_escalation_policy_mappingintegration option), and a per-service V3 webhook subscription back to Imbi. When a project dependency is added or removed in Imbi, it syncs the PagerDuty service dependencies.incidents— live-queries PagerDuty for the incidents on a project's service for the project-detail Incidents tab.webhook-actions— receives PagerDuty incident webhooks. v1 records events through the gateway and advertises no custom actions.analysis— the Project Doctor. It checks the service link, the service's escalation policy against the team mapping, and the service dependencies against Imbi'sDEPENDS_ONedges. Each problem it can repair has a Fix button.
Service dependencies
An Imbi A DEPENDS_ON B edge becomes a PagerDuty technical-service
dependency: A's service is the dependent service, and B's service is the
supporting service. Imbi removes a PagerDuty dependency only when both
services are linked to Imbi projects and Imbi has no DEPENDS_ON edge
between them. Dependencies on services that Imbi does not manage, and on
business services, stay as they are. A neighbour project with no
PagerDuty service is reported and skipped.
Bulk repair
The Apply Sync Fixes maintenance operation (Admin → Maintenance) runs the Doctor for every project, then applies only the fixes marked sweepable: the escalation-policy repoint and the dependency sync. It never creates or deletes a PagerDuty service.
The Imbi host discovers the package by the imbi_plugin_* naming
convention and reads the module-level PLUGIN attribute; there are no
entry points. All plugin base classes come from imbi_common.plugins.
Development
moon run root:setup # uv sync + pre-commit hooks
moon run pagerduty:test # coverage (fails under 85%)
moon run pagerduty:lint pagerduty:typecheck pagerduty:format # ruff + basedpyright + format check
Authentication is a PagerDuty REST API key (auth_type='api_token'),
configured as an encrypted plugin credential. PagerDuty is cloud-only, so
there is no host-flavor routing.
Metadata
Release files for imbi-plugin-pagerduty 2.39.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| imbi_plugin_pagerduty-2.39.0.tar.gz | 25.7 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| imbi_plugin_pagerduty-2.39.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.4 kB
Release files / imbi_plugin_pagerduty-2.39.0.tar.gz
| Download URL | imbi_plugin_pagerduty-2.39.0.tar.gz |
|---|---|
| Size | 25.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
910e6b153a2b4d2cb525ec31049740cf2f2b75abbe5b6e23149a524bbb31dd06
|
|
BLAKE2b-256 checksum How to use checksums |
5c7ab72bfe94c5abd82b4f54eb4812af879ee23466c124718a533cb7ce6eb750
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / imbi_plugin_pagerduty-2.39.0-py3-none-any.whl
| Download URL | imbi_plugin_pagerduty-2.39.0-py3-none-any.whl |
|---|---|
| Size | 23.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
701f549d81c202cd0b32ad273ec45b54156a7a2e04af699b44b9485e0d02fdb1
|
|
BLAKE2b-256 checksum How to use checksums |
810d8a80c522e89580af388b6a1920f1c71a15a9197b2c6e2e32c1dc6ec88e22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for imbi-plugin-pagerduty 2.39.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for imbi_plugin_pagerduty-2.39.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
