Enable deletion of customer alert data
Problem to solve
Adding Alerts to GitLab means that we need to be storing customer alert data in a database so that we can surface it in the GitLab UI. Customers send GitLab alerts via a REST endpoint. Their alerts may contain highly sensitive business information that they do not want stored in GitLab's database. It can be difficult to know what data is sent with alerts. In the scenario a customer sends us highly sensitive information they did not intend to we need to provide them a way to delete this data from our database.
This work drives the direction of the Alert Management category.
Provide customer with access to delete their alert data from the GitLab database or a streamlined process by which they can request deletion of this data via customer support.
Where this deletion field will live will depend on where we are at with #21914 and #214525 (closed). Essentially, if we implement this before those other issues are completed, the delete data section can just live underneath the existing alert endpoint configuration sections on Settings > Integrations > Alert Endpoints. However, if we are implementing it simultaneously with the other two mentioned issues, the deletion section will live in its own tab on Settings > Operations > Alerts:
|Add delete data section on Settings > Integrations > Alert Endpoints||Add delete data section on Settings > Operations > Alerts||Confirmation modal|
Note that the confirmation modal should appear regardless of which settings page we build this feature on.