Protei/PromucFlow_constructor
2
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

Merge pull request #14025 from appsmithorg/fix/migration_before_application_start

Browse Source 
Fix for running migrations before application start
This commit is contained in:
sidhantgoel 2022-05-23 16:58:27 +05:30 committed by GitHub
commit d60057af50
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
app/server/appsmith-server/src/main/java/com/appsmith/server/configurations/MongoConfig.java
View File

@ -51,8 +51,15 @@ import java.util.List;
repositoryBaseClass = BaseRepositoryImpl.class
)
public class MongoConfig {
/*
Changing this froom ApplicationRunner to InitializingBeanRunner
We are doing so because when one migration failed to run because API call executed before migration on old data
and made inconsistent for migration, having API calls run on unmigrated data is also a issue.
Link to documentation: https://docs.mongock.io/v5/runner/springboot/index.html
*/
@Bean
public MongockSpring5.MongockApplicationRunner mongockApplicationRunner(ApplicationContext springContext, MongoTemplate mongoTemplate) {
public MongockSpring5.MongockInitializingBeanRunner mongockInitializingBeanRunner(ApplicationContext springContext, MongoTemplate mongoTemplate) {
SpringDataMongoV3Driver springDataMongoV3Driver = SpringDataMongoV3Driver.withDefaultLock(mongoTemplate);
springDataMongoV3Driver.setWriteConcern(WriteConcern.JOURNALED.withJournal(false));
springDataMongoV3Driver.setReadConcern(ReadConcern.LOCAL);
@ -62,7 +69,7 @@ public class MongoConfig {
.addChangeLogsScanPackages(List.of("com.appsmith.server.migrations"))
.setSpringContext(springContext)
// any extra configuration you need
.buildApplicationRunner();
.buildInitializingBeanRunner();
}
@Bean