Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
All the configurations start on a database property disabled
See original GitHub issueI’ve noticed that all the AutoConfiguration classes have annotation like this @ConditionalOnProperty(name = "embedded.postgresql.enabled", matchIfMissing = true)
It is not affected by the actual value of enabled as it is expected to disable the start of configuration.
If it was supposed to disable start with the property embedded.containers.enabled and annotations
@ConditionalOnExpression("${embedded.containers.enabled:true}" than:
- It has ambiguous naming. Why should we have
embedded.postgresql.enabledif it doesn’t affect anything actually? - If I want to start multiple amounts of different containers then it is not possible as either, I disable all the configurations with
embedded.containers.enabledor keep enabled all of it.
Thus, I suggest expecting true for each auto-configuration:
@ConditionalOnProperty(name = "embedded.postgresql.enabled", havingValue = "true", matchIfMissing = true)
Expected:
| Setting1 | Setting2 | Outcome |
|---|---|---|
| embedded.containers.enabled=false | embedded.memsql.enabled=true embedded.mysql.enabled=true | Memsql wil not start, mySql will not start |
| embedded.containers.enabled=true | embedded.memsql.enabled=false embedded.mysql.enabled=true | Memsql will not start, mySql will start |
| embedded.containers.enabled=true | embedded.memsql.enabled=true, embedded.mysql.enabled=true | Memsql will start, mySql will start |
| embedded.containers.enabled is missing | embedded.memsql.enabled is missing | Memsql will start |
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I see, please add container disabling property directly to you gradle junit task likewise
systemProperty("spring.profiles.active", "mysql, test")The init phase of spring boot container is bootstrap phase of spring boot app, which comes right before the application phase. application properties are red only on application phase of your app, whereas bootstrap properties are read on bootstrap phase, so either you need to add additional set of
bootstrap-{db}.propertiesfiles, or set as program variables or systems onesall containers are enabled by default, you need to disable unneeded, not enable needed =)