Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I noticed a different behavior of the property spring.cloud.bootstrap.location since Spring Boot 2.x

Behavior in Spring Boot 1.x:

  • Build in bootstrap.properties file inside the JAR is regarded
  • Specified bootstrap.properties file is regarded
  • Behavior in Spring Boot 2.x:

  • Build in bootstrap.properties file inside the JAR is not regarded
  • Specified bootstrap.properties file is regarded
  • Reason is that since Spring Boot 2 the behavior of the spring.config.location configuration has been fixed and the property spring.cloud.bootstrap.location works now also as desired.

    See https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.0-Migration-Guide#configuration-location

    I restored the origin behavior by adding the default search locations to the property in addition spring.cloud.bootstrap.location=classpath:/,classpath:/config/,file:./,file:./config/,file:/my/special/search/location

    Should there be introduced also a new property spring.cloud.bootstrap.additional-location like the spring.config.additional-location ?

    Hint: This is how the BootstrapApplicationListener currently works:

    https://github.com/spring-cloud/spring-cloud-commons/blob/57c2f9a154f3d4146135529261f071a00ab47ea9/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/BootstrapApplicationListener.java#L145-L156

    Thanks for contributing an answer to Stack Overflow!

    • Please be sure to answer the question . Provide details and share your research!

    But avoid

    • Asking for help, clarification, or responding to other answers.
    • Making statements based on opinion; back them up with references or personal experience.

    To learn more, see our tips on writing great answers .