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.3.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.3.0
File Size Uploaded Provenance Actions
pulumi_incident-0.3.0.tar.gz 517.6 kB Without provenance Details for pulumi_incident-0.3.0.tar.gz

Built distribution (wheel)

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

Total release size: 1.1 MB

Release files / pulumi_incident-0.3.0.tar.gz

Download URL pulumi_incident-0.3.0.tar.gz
Size 517.6 kB
Tags Source
SHA-256 checksum
How to use checksums
368a0c1d2d22b5474c0c5603b5314d7b58cfa9ee96c7643d19cd0b4aeb42dd3c
BLAKE2b-256 checksum
How to use checksums
d9973b66a7ac9d4cf969fdad44c92970cabb67ba87a22797d3aecf326a22bb6a
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.3.0-py3-none-any.whl

Download URL pulumi_incident-0.3.0-py3-none-any.whl
Size 612.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c20100c54e82a16eb26b78ab7eec28ea9fb72e4060913da796792f211b917c9b
BLAKE2b-256 checksum
How to use checksums
7964f10f472922fd761ca2cf61fe5a2db1d9715295e2ef070006da60cd7a9e79
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.3.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