create-pagerduty-incident

This action will create a PagerDuty incident. Only one service can be targeted at a time.

Index

• create-pagerduty-incident
  • Inputs
  • Outputs
  • Usage Examples
  • Contributing
    • Incrementing the Version
    • Source Code Changes
    • Recompiling Manually
    • Updating the README.md
  • Code of Conduct
  • License

Inputs

Parameter	Is Required	Description
pagerduty-api-key	true	The PagerDuty API Key that allows access to your services.
email	true	The email address of a valid PagerDuty user on the account associated with the auth token.
service-id	true	The PagerDuty Service ID to create the incident for.
title	true	The title of the PagerDuty Incident that will be created.
body	false	The body of the PagerDuty Incident that will be created.
urgency	false	The urgency of the incident. Accepts: high or low. Defaults to high.

Outputs

Output	Description
incident-id	The ID of the PagerDuty Incident that was just created.
pagerduty-error-code	The status code of the PagerDuty API request if it returns an error.

Usage Examples

  jobs:
    validate-deployed-code:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3

      - id: deployed-checksum
        run: ./generate-checksum-against-deployed-code.sh

      - id: compare-checksums
        run: ./compare-checksums -deployedChecksum ${{ steps.deployed-checksum.outputs.CHECKSUM }}

      - name: Create a PagerDuty Incident
        if: steps.compare-checksums.outputs.MATCH == 'false'
        # You may also reference the major or major.minor version
        uses: im-open/[email protected]
        with:
          pagerduty-api-key: ${{secrets.PAGERDUTY_API_KEY}}
          email: [email protected]
          service-id: 'P0ABCDE'
          title: 'The deployed code does not match the expected version'
          body: 'Find more information at: https://github.com/${{ github.repository }}/actions/runs/${{ github.run_id }}'
      

Contributing

When creating PRs, please review the following guidelines:

• The action code does not contain sensitive information.
• At least one of the commit messages contains the appropriate +semver: keywords listed under Incrementing the Version for major and minor increments.
• The action has been recompiled. See Recompiling Manually for details.
• The README.md has been updated with the latest version of the action. See Updating the README.md for details.

Incrementing the Version

This repo uses git-version-lite in its workflows to examine commit messages to determine whether to perform a major, minor or patch increment on merge if source code changes have been made. The following table provides the fragment that should be included in a commit message to active different increment strategies.

Increment Type	Commit Message Fragment
major	+semver:breaking
major	+semver:major
minor	+semver:feature
minor	+semver:minor
patch	default increment type, no comment needed

Source Code Changes

The files and directories that are considered source code are listed in the files-with-code and dirs-with-code arguments in both the build-and-review-pr and increment-version-on-merge workflows.

If a PR contains source code changes, the README.md should be updated with the latest action version and the action should be recompiled. The build-and-review-pr workflow will ensure these steps are performed when they are required. The workflow will provide instructions for completing these steps if the PR Author does not initially complete them.

If a PR consists solely of non-source code changes like changes to the README.md or workflows under ./.github/workflows, version updates and recompiles do not need to be performed.

Recompiling Manually

This command utilizes esbuild to bundle the action and its dependencies into a single file located in the dist folder. If changes are made to the action's source code, the action must be recompiled by running the following command:

# Installs dependencies and bundles the code
npm run build

Updating the README.md

If changes are made to the action's source code, the usage examples section of this file should be updated with the next version of the action. Each instance of this action should be updated. This helps users know what the latest tag is without having to navigate to the Tags page of the repository. See Incrementing the Version for details on how to determine what the next version will be or consult the first workflow run for the PR which will also calculate the next version.

Code of Conduct

This project has adopted the im-open's Code of Conduct.

License

Copyright © 2024, Extend Health, LLC. Code released under the MIT license.