Run one SQL file per changeset (Liquibase #5) 49/141549/1 master
authordanielhanrahan <daniel.hanrahan@est.tech>
Thu, 17 Jul 2025 10:37:16 +0000 (11:37 +0100)
committerdanielhanrahan <daniel.hanrahan@est.tech>
Thu, 17 Jul 2025 14:57:44 +0000 (15:57 +0100)
commit33b84a92b0364e344c3057f3f895018f8a12d805
treee85fe63f2f3bb5380a045771934698a0f34c89a7
parent2039302bc25821eee1139fb80a41d26ab7365e3e
Run one SQL file per changeset (Liquibase #5)

Following Liquibase best practices, separate changes are made
as separate changesets. To allow upgrade from DB-migrator, many
preconditions are added to mark changes as ran if already done.

Issue-ID: POLICY-5398
Change-Id: I535ab6f8497d0528ed98a2b4b04fa4163065bcdf
Signed-off-by: danielhanrahan <daniel.hanrahan@est.tech>
runtime-acm/src/main/resources/db/changelog/changelog-1400.yaml
runtime-acm/src/main/resources/db/changelog/changelog-1500.yaml
runtime-acm/src/main/resources/db/changelog/changelog-1600.yaml
runtime-acm/src/main/resources/db/changelog/changelog-1601.yaml
runtime-acm/src/main/resources/db/changelog/changelog-1700.yaml
runtime-acm/src/main/resources/db/changelog/changelog-1701.yaml