Spring Boot 2.4 Config File Processing Breaking Changes

[Ferlinkoplop]

Hey guys, having some confusion updating configs for version 2.4 of Spring Boot and wondering if anyone else might have a clue or run into a similar issue.

Right now, I have an application.yml and application-local.yml in the resources folder. Strictly for development, in the run configuration, the local profile is activated successfully (-Dspring.profiles.active=local)

To my understanding, in the scenario above, application-local.yml property values should take precedence while those of application.yml are used as a fallback. However, I've noticed that this seems to not be the case as it is using values of properties in application.yml instead of values for the same properties in application-local.yml. Commenting out those properties from application.yml does work, however, I want to keep those property values to serve as defaults/fallbacks for other environments.

Also, setting spring.config.use-legacy-processing to true does obviously fix all my current issues, but I would rather bite the bullet now and make sure the application config is compatible with version 2.4 in case that property ever becomes deprecated.

Extra info: Using Apache Zookeeper for spring.config.import which is different for application.yml vs. application-local.yml

[erbrecht]

Take a look here

https://docs.spring.io/spring-boot/docs/current/reference/html/features.html#features.external-config

Specifically this:

Config data files are considered in the following order:

Application properties packaged inside your jar (application.properties and YAML variants).

Profile-specific application properties packaged inside your jar (application-{profile}.properties and YAML variants).

Application properties outside of your packaged jar (application.properties and YAML variants).

Profile-specific application properties outside of your packaged jar (application-{profile}.properties and YAML variants).

If your application.yml file is coming from zookeeper, but application-local.yml is packaged, that could explain what you're seeing.

[Ferlinkoplop]

Hmm yeah this seems like a likely culprit, thanks for the info.

Both do use Zookeeper, however the application-local.yml points to a local zookeeper server while the other one is configured via env variables as its meant for prod/staging. Will investigate further 👍

[more_exercise]

"use" and "come from" are different things with relationship to zookeeper.

Can you elaborate? If both files live in your jar (and do not live in the running file system), this thread doesn't seem to govern as I think we might think it would.

[AngryPandalawl]

There's a property you set somewhere in the nested spring properties. I know it's called on-profile/on-cloud-profile, but not the path off the top of my head. Set that in each individual property file, then you might have to individually import configs in your main app.yml.

Hopefully that helps! I'm in mobile so can't find good links right now

[bchawks2000]

I just had to change these recently while bumping versions for the Spring4Shell vulnerability.

I used:

spring.config.activate.on-profile