library
turbot/pagerduty
OverviewPipelines
0
Triggers
0
Variables
GitHub

Create Incident

Create an incident.

Run the pipeline

To run this pipeline from your terminal:

flowpipe pipeline run pagerduty.pipeline.create_incident \
--arg 'service_id=<string>' \
--arg 'service_type=<string>' \
--arg 'title=<string>' \
--arg 'from=<string>'

Use this pipeline

To call this pipeline from your pipeline, use a step:

step "pipeline" "step_name" {
pipeline = pagerduty.pipeline.create_incident
args = {
service_id = <string>
service_type = <string>
title = <string>
from = <string>
}
}

Params

NameTypeRequiredDescriptionDefault
credstringYesName for credentials to use. If not provided, the default credentials will be used.default
service_idstringYesThe ID of the service.-
service_typestringYesThe type of the service.-
titlestringYesA succinct description of the nature, symptoms, cause, or effect of the incident.-
fromstringYesThe email address of a valid user associated with the account making the request.-
bodystringNoAdditional incident details.-
body_typestringNoThe type of the body.-
conference_numberstringNoThe phone number of the conference call for the conference bridge.-
conference_urlstringNoAn URL for the conference bridge. This could be a link to a web conference or Slack channel.-
escalation_policy_idstringNoThe ID of the escalation policy for the incident.-
escalation_policy_typestringNoThe type of the escalation policy for the incident.-
incident_keystringNoA string which identifies the incident. Sending subsequent requests referencing the same service and with the same incident_key will result in those requests being rejected if an open incident matches that incident_key.-
priority_idstringNoThe ID of the priority of the incident.-
priority_typestringNoThe type of the priority of the incident.-
urgencystringNoThe urgency of the incident. Allowed values are 'high' and 'low'.-

Outputs

NameDescription
incidentThe created incident.

Tags

type = featured