Add domain column to alerts table
What does this MR do?
Add a column called domain to alerts table we want to apply different logics to different types of alerts.
This migration will be used to implement in two different places for protect team
Related issue
Migrations
UP
== 20201203123524 AddDomainEnumToAlerts: migrating ============================
-- add_column(:alert_management_alerts, :domain, :integer, {:limit=>2, :default=>0})
-> 0.0040s
== 20201203123524 AddDomainEnumToAlerts: migrated (0.0114s) ===================
== 20201203171631 AddIndexToDomain: migrating =================================
-- transaction_open?()
-> 0.0000s
-- index_exists?(:alert_management_alerts, :domain, {:name=>"index_alert_management_alerts_on_domain", :algorithm=>:concurrently})
-> 0.0088s
-- execute("SET statement_timeout TO 0")
-> 0.0003s
-- add_index(:alert_management_alerts, :domain, {:name=>"index_alert_management_alerts_on_domain", :algorithm=>:concurrently})
-> 0.0179s
-- execute("RESET ALL")
-> 0.0004s
== 20201203171631 AddIndexToDomain: migrated (0.0282s) ========================
Down
== 20201203123524 AddDomainEnumToAlerts: reverting ============================
-- remove_column(:alert_management_alerts, :domain, :integer, {:limit=>2})
-> 0.0040s
== 20201203123524 AddDomainEnumToAlerts: reverted (0.0120s) ===================
== 20201203171631 AddIndexToDomain: reverting =================================
-- transaction_open?()
-> 0.0000s
-- index_exists?(:alert_management_alerts, "index_alert_management_alerts_on_domain", {:algorithm=>:concurrently})
-> 0.0079s
== 20201203171631 AddIndexToDomain: reverted (0.0095s) ========================
Production Data
gitlabhq_production=> select count(id) from alert_management_alerts;
count
-------
90_071
(1 row)
Conformity
Edited by Can Eldem