port-labs/Port PagerDuty Incident Action
GitHub action to create repositories templated with Cookiecutter with Port integration
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Aug 8, 2023
- License
- None
Pinned Snippet
uses: port-labs/pagerduty-incident-gha@a1146f28039cec6bb878c5b975161b39e0829401 # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| token | The Pager Duty Token to use to authenticate with the API with permissions to create incidents | yes | — |
| portClientId | The Port Client ID to use to authenticate with the API | yes | — |
| portClientSecret | The Port Client Secret to use to authenticate with the API | yes | — |
| blueprintIdentifier | The blueprint identifier to use to populate the Port relevant entity | no | pagerdutyIncident |
| incidentTitle | The title of the incident to create | yes | — |
| extraDetails | Extra details about the incident to create | no | — |
| service | The service id to correlate the incident to | yes | — |
| urgency | The urgency of the incident to create | no | high |
| actorEmail | The email of the actor to create the incident with | yes | — |
| portRunId | Port run ID to came from triggering the action | yes | — |
Outputs
no outputs