This release is a pre-release and may not be stable for production use.
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
- Registry docs for per-resource reference
- API docs for what the underlying API supports
- Issues here for packaging problems, or terraform-provider-incident for resource behaviour, since that is where resources are implemented
CONTRIBUTING.md covers building and regenerating the SDKs.
MIT licensed. See LICENSE.
Metadata
Release files for pulumi-incident 1.0.0a1791192829
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 | Actions |
|---|---|---|---|---|
| pulumi_incident-1.0.0a1791192829.tar.gz | 491.8 kB | Without provenance | Details for pulumi_incident-1.0.0a1791192829.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pulumi_incident-1.0.0a1791192829-py3-none-any.whl | Python 3 | none | any | Details for pulumi_incident-1.0.0a1791192829-py3-none-any.whl |
Total release size: 1.1 MB
Release files / pulumi_incident-1.0.0a1791192829.tar.gz
| Download URL | pulumi_incident-1.0.0a1791192829.tar.gz |
|---|---|
| Size | 491.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c6b420fe9239eb5dbc9f002ff46279a851d069be67c465bc9583bad1d1c90660
|
|
BLAKE2b-256 checksum How to use checksums |
616db8330d1d7f91b11798316ce2b6bab600d379ca2ef7aa649d15aa3c531d4d
|
| 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-1.0.0a1791192829-py3-none-any.whl
| Download URL | pulumi_incident-1.0.0a1791192829-py3-none-any.whl |
|---|---|
| Size | 578.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7bb85d9a644e59281a3ab75a233f4cb4062e7e8b900f8ac6e45a4257df46865a
|
|
BLAKE2b-256 checksum How to use checksums |
c5443048edd1e3ffa21e3b164af663ff4465238c53b7aae9f25234c873b9b483
|
| 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 1.0.0a1791192829
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.