fix(db): bring back custom migrations migrations

Ref: SRX-C0R01N

Author: AminSlk

database/migrations/postgres/1738234757185160_remove_custom_migrations.down.sql

@@ -0,0 +1,5 @@
+CREATE TABLE IF NOT EXISTS custom_migration_cutoff
+(
+    migration_done_at TIMESTAMP NOT NULL,
+    kuberpult_version varchar(100) PRIMARY KEY -- the version as it appears on GitHub, e.g. "1.2.3"
+);

database/migrations/postgres/1738234757185160_remove_custom_migrations.up.sql

@@ -0,0 +1 @@
+DROP TABLE IF EXISTS custom_migration_cutoff;

database/migrations/postgres/1738337211474834_commit_events.up.sql

@@ -0,0 +1,10 @@
+DO $$
+BEGIN
+    IF NOT EXISTS (
+        SELECT 1 FROM event_sourcing_light LIMIT 1
+    ) THEN
+        INSERT INTO event_sourcing_light (eslversion, created, event_type, json)
+        VALUES (0, now(), 'MigrationTransformer', '{"eslVersion":0,"metadata":{"authorEmail":"Migration","authorName":"Migration"}}');
+    END IF;
+END
+$$;

database/migrations/postgres/1738337211474835_commit_events.up.sql

@@ -0,0 +1,10 @@
+DO $$
+BEGIN
+    IF NOT EXISTS (
+        SELECT 1 FROM commit_events LIMIT 1
+    ) THEN
+        INSERT INTO commit_events (uuid, timestamp, commitHash, eventType, json, transformereslVersion)
+        VALUES ('00000000-0000-0000-0000-000000000000', now(), '0000000000000000000000000000000000000000', 'db-migration', '{}', 0);
+    END IF;
+END
+$$;

docs/rollback.md

@@ -12,3 +12,5 @@ You can easily roll back to an older version of a single service
 ![](../assets/img/rollback/releasedialog-full.png)
 5) Now you have 2 planned actions, that you still need to apply. ![](../assets/img/rollback/planned-actions.png)
 
+# Migrations
+If you want to use custom migrations you can use [custom_migrations down migration](../database/migrations/postgres/1738234757185160_remove_custom_migrations.down.sql)