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.
Allow manually setting of MongoDB instead of using Autowired details
See original GitHub issueCurrently JaversMongoAutoConfiguration.java forces you to use the autowired MongoClient (and MongoProperties). This is fine if you want to have javers auditing in the same host:DB as your primary mongoDB.
We have a use case where we want to keep the (javers) auditing DB and primary MongoDB separate and for that we want to be able to pass in mongo credentials from the properties file (e.g. with javers.uri) that will cause the autoconfig class to create a MongoClient instead of using the autowired instance.
What are the thoughts on this? Would be happy to submit a pull-request.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 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
fixed in 5.6.0 see https://javers.org/documentation/spring-boot-integration/#starter-repository-configuration
@bartoszwalacik Have a look at the PR and let me know how it looks.