chore: migrate legacy controlled seeds to Flyway - #50
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
旧手工初始化文件中的 25 条受控种子记录不在 Flyway baseline 中，直接删除会使新库缺少验证码场景、通知模板和常用字典。本变更新增保留管理员现有数据的版本化 DML，删除旧建库文件并修正文档。
验证：隔离 MySQL 中新库与 0.6/0.7 升级迁移均通过
flyway validate；新库断言 25 条记录齐全，重复migrate零变更；mvn clean package -DskipTests通过。关联 opensabre/base-k8s#38。