Issue Summary

When customer's PagerDuty API key becomes invalid (either an actual change, or a PagerDuty incident), Statuspage will prompt for a new API Key for this integration. When reactivating the PagerDuty integration, under certain conditions the original PagerDuty integration is updated with the new API key and a new PagerDuty integration is created resulting in duplicate PagerDuty integrations.

This will cause unexpected behaviours in Statuspage as the UI will display one of the multiple PagerDuty Integrations, and customers can end up configuring services across all the PagerDuty integrations leading to multiple incidents being created from a single PagerDuty Service

Steps to Reproduce

1. Have a PagerDuty integration with an invalid API, and recreate a new PagerDuty Integration. Note: this is believed to have been remediated since this Bug was discovered.
2. Trigger the open and close of a number of Pagerduty actions which trigger Statuspage Incident creation
3. Eventually a duplicate incident will be created.

Expected Results

Normally there should never be a duplicate incident.

Actual Results

Sometimes a duplicate incident will be created.

Workaround

There is no workaround known at this time and customers who were affected by this face the unfortunate situation of having their pagerduty integrations purged and recreated while we work out a final solution and remediation path