如果配置文件设置不更改为 application-default.properties，如何忽略 application.properties 值

Question

I am using spring profiles to load configurations based on the environment and when reading using Autowired Environment object, it seems additional to environment specific values, Spring also pass values from application.properties, the same is mentioned in spring document Profile-specific Properties and also here in this answer , but I cannot change to application-default.properties because of below limitation.

The problem/limitation for me is the deployment platform(rules) that I am using, for all environment the environment the identifier will be passed as JVM arguments, but for production it will not be passed, as mentioned below

application-dev.properties --> DEV environment will pass this -Dspring.profiles.active=dev
application-qa.properties --> QA environment will pass this -Dspring.profiles.active=qa
application.properties --> PROD environment won't pass any argument

The option I am having now is to have keys in application.properties with empty values in other environment specific properties file(event not used)and handle in code, other than this is there any other elegant way to handle without change application.properties

Answer 1

As the linked documentation ( Profile-specific Properties ) says, application.properties is always loaded.

As it also says, if no active profile has been set (eg using -Dspring.profiles.active ), the default profile is automatically made active.

As the section Adding Active Profiles says, you can have a profile-specific property add active profiles with the spring.profiles.include property.

This means that you can have the default profile property file activate a prod profile, like this:

File application-default.properties :

spring.profiles.include = prod

If you have that file, then running without -Dspring.profiles.active set will load properties from these files (in order):

application-prod.properties
application-default.properties
application.properties

If you run with -Dspring.profiles.active=dev , properties are loaded from these files (in order):

application-dev.properties
application.properties

By doing that, you now have a well-named profile-specific property file for each of your environments:

application-dev.properties  --> since DEV environment passed -Dspring.profiles.active=dev
application-qa.properties   --> since QA environment passed -Dspring.profiles.active=qa
application-prod.properties --> since PROD environment didn't pass -Dspring.profiles.active

The application.properties file is still loaded, and should contain all non-environment-specific properties, ie all common properties, as well as default values for any global properties that might have environment-specific values (overrides).

The application-<profile>.properties files can add environment-specific properties, and can override global properties that needs a different value than the default specified in the application.properties file.