#7103 [v2] DB migration with version Pull request opened by machichima Tracking issue Why are the changes needed? We will run migration every time we start, we should only do this if schema changed. What changes were proposed in this pull request? 1. add run/cache service DB migration list 2. use

gormigrate

to migrate. This will only perform migration on new entity, and will not apply migration every time How was this patch tested? Run sandbox locally and make sure we do not overwhelming SQL string image Labels Please add one or more of the following labels to categorize your PR: • added: For new features. • changed: For changes in existing functionality. • deprecated: For soon-to-be-removed features. • removed: For features being removed. • fixed: For any bug fixed. • security: In case of vulnerabilities This is important to improve the readability of release notes. Setup process Screenshots Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. Related PRs Docs link •

main

• #6583 • [v2] DB migration with version 👈 flyteorg/flyte