No CLI entrypoint

[cmclaughlin]

Hello,

Following this tutorial, I was expecting to get a "pagerduty " CLI entrypoint after installing the package via pip.

https://www.pagerduty.com/docs/guides/monit-integration-guide/

This is my first time installing and/or using this package... but it seems that the package either went through a big refactor recently and/or switched from a community developed project to something more official? Either way, it would be nice to either add a CLI entrypoint or update the tutorial.

Thanks

[Deconstrained]

Hello @cmclaughlin, thank you for reporting this issue. The integration depends on a legacy / abandoned version of pagerduty. However, to restore the Monit integration, I will investigate adding a script to the package that can be used for sending PagerDuty events, so that it can continue to be used in the Monit integration.

In the mean time (and pardon the hackiness), a really basic curl script could replace the /usr/local/bin/pagerduty in the pagerduty-trigger and pagerduty-resolve scripts referenced in the integration guide. The command in the scripts look like this:

/usr/local/bin/pagerduty -k "$PAGERDUTY_SERVICE_KEY" -i "$INCIDENT_KEY" --description="$DESCRIPTION" trigger

In other words, all it needs to do is take a -k argument that is the routing key, an -i argument that would be the deduplication key, a --description argument that sets the summary and a positional argument trigger or resolve. For Events API v2 one would also need an argument to populate the source field in the event, or it could be hard coded or based on an environment variable.