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.
@TestPropertySource vs spring-cloud-config
See original GitHub issueThis doc don not have information about spring-cloud-config… http://docs.spring.io/spring-boot/docs/current/reference/html/boot-features-external-config.html
I know that spring-cloud-config will add itself first by default. https://github.com/spring-cloud/spring-cloud-commons/blob/master/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/config/PropertySourceBootstrapConfiguration.java#L155
But I thank that spring-cloud-config default order should be the same as JNDI.
Default spring-cloud-config order > @TestPropertySource, This will make people very confused.
I think overrideSystemProperties is not a good way.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (3 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
@spencergibb We would like to also use cloud config for integration tests, but in some tests we need to override a couple of properties. Is that possible? Thx!
For unit tests: Agreed. But for system tests I am not so sure.