-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Liquibase actuator endpoint does not give correct information when multiple databases are used in one project #19171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Liquibase actuator endpoint does not give correct information when multiple databases are used in one project #19171
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. If you have time, could you please look at adding a test for multiple datasources that reproduces the problem and verifies the fix?
Sure, I test in local, and see if there is an easy way to migrate to test. |
For the original LiquibaseEndpoint code, this test returns:
For the fixed code, it can pass the test correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great stuff. Thanks very much, @polarbear567.
Previously, the endpoint used the same change log history service for for each SpringLiquibase bean that it processed. This resulted in pollution of the reported changes as the history of each bean was not isolated. This commit updates the endpoint to use a new history service for each SpringLiquibase bean that is processed. See gh-19171
Thanks again, @polarbear567. The proposed changes have been merged into 2.1.x and forwards to 2.2.x and master. |
No description provided.