Skip to content

Commit dc5ce7a

Browse files
committed
fix(migrations): add instructions to bring back custom_migration_cutoff
Ref: SRX-C0R01N
1 parent 7e27172 commit dc5ce7a

5 files changed

+9
-27
lines changed

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

-5
This file was deleted.

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

-1
This file was deleted.

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

-10
This file was deleted.

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

-10
This file was deleted.

docs/rollback.md

+9-1
Original file line numberDiff line numberDiff line change
@@ -13,4 +13,12 @@ You can easily roll back to an older version of a single service
1313
5) Now you have 2 planned actions, that you still need to apply. ![](../assets/img/rollback/planned-actions.png)
1414

1515
# Migrations
16-
If you want to use custom migrations you can use [custom_migrations down migration](../database/migrations/postgres/1738234757185160_remove_custom_migrations.down.sql)
16+
If you've deleted the custom migrations cutoff table and you want to bring it back you can run:
17+
```Sql
18+
CREATE TABLE IF NOT EXISTS custom_migration_cutoff
19+
(
20+
migration_done_at TIMESTAMP NOT NULL,
21+
kuberpult_version varchar(100) PRIMARY KEY -- the version as it appears on GitHub, e.g. "1.2.3"
22+
);
23+
```
24+
This way you can have this table back.

0 commit comments

Comments
 (0)