Add Liquibase support and legacy -> Jersey DB migration#548
Open
this-Aditya wants to merge 7 commits intoci-setupfrom
Open
Add Liquibase support and legacy -> Jersey DB migration#548this-Aditya wants to merge 7 commits intoci-setupfrom
this-Aditya wants to merge 7 commits intoci-setupfrom
Conversation
dosubot
bot
added
size:XXL
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.
Added Liquibase support for appserver jersey and microservices. liquibase currently handles database migration from the legacy appServer (spring) to the appserver jersey implementation.
This PR does not include support for migration from appserver jersey to microservices yet, as it is not finalized whether such migration is required. The entity relationships in the microservices architecture differ from those in the spring and jersey versions, so if this migration becomes necessary it will require further discussion.
Liquibase has been tested with jersey and works correctly, but microservices integration has not yet been tested. I plan to validate the migration locally first before running it in other environments.
Liquibase support for quartz scheduler tables has not been added for microservices yet. Currently quartz is included as an
apidependency in core that gets passed to every microservice, which would require adding the liquibase scripts to each service. A better approach would be to reduce the quartz dependency scope to only the services that require it and then add liquibase support for the quartz tables. This will be implemented once the final approach is decided.