Skip to main content

Pulumi provider for incident.io

Manage incident.io configuration as code from a Pulumi program, in TypeScript, Python or Go.

Generated from terraform-provider-incident, so anything you can manage with Terraform you can manage here.

Install

npm install @incident-io/pulumi
pip install pulumi-incident
go get github.com/incident-io/pulumi-incident/sdk/go/incident

Configure

Create an API key in Settings → API keys, then either:

pulumi config set --secret incident:apiKey inc_...
# or
export INCIDENT_API_KEY=inc_...

On a dedicated or self-hosted deployment, also set incident:endpoint.

Example

import * as incident from "@incident-io/pulumi";

const trivial = new incident.Severity("trivial", {
    name: "Trivial",
    description: "Issues causing no impact.",
    rank: 1,
});

Per-resource reference and examples in all three languages are on the Pulumi Registry page.

What you can manage

Escalation paths, schedules and schedule sync rules. Alert sources, routes and attributes. Catalog types, attributes and entries. Severities, statuses, incident roles, custom fields. Workflows, maintenance windows, policies, secrets and API keys.

Resources with Beta in the name track features still changing in the product, and their inputs may change in a minor release.

Import existing configuration

Every resource supports pulumi import:

pulumi import incident:index/severity:Severity trivial 01ABCDEF...

Importing claims the resource as managed by code, which stops it being edited in the dashboard. That claim is a write to your account, so set markImportedResourcesAsManaged to false if you would rather imports left it untouched.

Moving from the Terraform bridge

If you use pulumi package add terraform-provider incident-io/incident today, this package replaces it. Resource names and properties are the same, so your program does not change. Remove the packages entry from Pulumi.yaml, delete the generated SDK, and install the published package.

Help

CONTRIBUTING.md covers building and regenerating the SDKs.

MIT licensed. See LICENSE.

Metadata

Release files for pulumi-incident 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pulumi-incident 0.5.0
File Size Uploaded Provenance Actions
pulumi_incident-0.5.0.tar.gz 536.9 kB Without provenance Details for pulumi_incident-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for pulumi-incident 0.5.0
File Interpreter ABI Platform Actions
pulumi_incident-0.5.0-py3-none-any.whl Python 3 none any Details for pulumi_incident-0.5.0-py3-none-any.whl

Total release size: 1.2 MB

Release files / pulumi_incident-0.5.0.tar.gz

Download URL pulumi_incident-0.5.0.tar.gz
Size 536.9 kB
Tags Source
SHA-256 checksum
How to use checksums
58bd3706f53b3aaff152fc853882eb0936b3767b71d7c8856d3e5bd907bdd8f9
BLAKE2b-256 checksum
How to use checksums
79f0bff49704e1132bb3ff93f00dae0ecc992e254b5525a1f91f4ec74d1a6dfa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.11

Release files / pulumi_incident-0.5.0-py3-none-any.whl

Download URL pulumi_incident-0.5.0-py3-none-any.whl
Size 639.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
255c4a64e1955c5f5f9d8c29966fa76a1f6042f1619c722933c1dde800d85d62
BLAKE2b-256 checksum
How to use checksums
4f9a20cc79a7654152547b875edfbd410574e5ebcd4d864527398a751fb1c70d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.11

Security for pulumi-incident 0.5.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page