Skip to content

How to migrate/deprecate Opsgenie integration

Overview

We are adding the ability to create and customize mutiple HTTP endpoints. We are going to replace the existing and useless Opsgenie integration with this functionality. This will allow us to deprecate the existing Opsgenie integraiton. Users will be able to create an HTTP endpoint if they want to see Opsgenie alerts in GitLab.

Migration Plan

We need to figure out how to deprecate the current opsgenie integration UI with the release of &4390 (closed). I want to minimize additional work by design and engineering to maintain it for any amount of time. But we do need to provide our users time to migrate themselves.

SO, I think that we will need at least one month of overlap.

Proposal

  1. Build &4390 (closed) and include Opsgenie as an option in the drop-down => this is essentially moving the existing functionality to the new paradigm. Release it in 13.X. Post a deprecation notice in the same release post
  2. In 13.x+1, remove Opsgenie as an option in the drop-down. Post a deprecation notice in the release post with a link to documentation on how to use the new Custom Integrations functionality to surface opsgenie alerts in GitLab.