v1.4.0 - Configurable PD priority to Zabbix severity mapping

Made it configurable whether or not to update Zabbix event Severity when PagerDuty incident Priority is changed, and made the mapping of priorities to severities configurable.

Configurable mapping is needed if PD is configured with priorities other than P1-P5. Our setup has PD priorities that are very similar to our Zabbix severities.

Full Changelog: v1.3.0...v1.4.0

v1.3.0

What's Changed

• Change to trying multiple zabbix urls in order by @eric-eisenhart in #9
• Add support for handling multi-alert incidents, more ways to find the eventid, and for pagerduty incident merging by @eric-eisenhart in #10

Full Changelog: v1.2.1...v1.3.0

v1.2.1

• Change close from "send close and message" to "send ack and message; then send separate close".
  This way, non-closable Zabbix events still get ACK'd with a "resolved" comment in Zabbix.
• Try a couple backup options for getting the zabbix event id from the pager duty incident details.
• Also additional debugging stuff, especially around retrying talking to zabbix API

Full Changelog: v1.1.2....v1.2.1

v1.1.2

What's Changed

• Update docs, by @eric-eisenhart in #4
• Be smarter about success headers, by @eric-eisenhart in #3
• SOC-2919 code cleanup by @eric-eisenhart in #5

Full Changelog: v1.1.1...v1.1.2

1.1.1: Debug output cleanup

What's Changed

• SOC-2919 debug output cleanup by @eric-eisenhart in #2

Full Changelog: v1.1.0...v1.1.1

1.1: Validate auth token (security)

What's Changed

• Authentication token verification by @eric-eisenhart in #1

Full Changelog: v1.0.0...v1.1.0

1.0.0: it works

This is working for me in a dev environment, and I think instructions are adequate for getting it set up...