Bootstrap、Application 以及自定義配置屬性的優先級對比

bootstrap配置文件和application配置文件優先級

bootstrap優先級<application優先級

bootstrap、application和自定義配置屬性優先級

自定義配置屬性：

public class NacosDiscoveryPrepareApplicationListener implements ApplicationListener<ApplicationPreparedEvent>, Ordered {
@Override
    public void onApplicationEvent(ApplicationPreparedEvent event) {
        ConfigurableEnvironment environment = event.getApplicationContext().getEnvironment();           
Map<String, Object> cloudNacosDiscoveryProperties = new HashMap<>();
            cloudNacosDiscoveryProperties.put("spring.cloud.nacos.discovery.enabled", "false");
            cloudNacosDiscoveryProperties.put("spring.cloud.nacos.discovery.register-enabled", "false");
            environment.getPropertySources().addLast(new MapPropertySource("edsp.cloud.nacos.discovery", cloudNacosDiscoveryProperties));
}
}

自定義配置屬性中通過addLast()方法添加配置屬性，優先級是最低的，也就是自定義<bootstrap<application

也可以通過addFirst()方法添加配置屬性，優先級是最高的，也就是bootstrap<application<自定義

也可以通過addBefore()或者addAfter()方法將配置的優先級指定放在某個配置名之前；比如：

public static void bootStrapPropertySource(ConfigurableEnvironment configurableEnvironment, Map map, String name) {
        MutablePropertySources propertySources = configurableEnvironment.getPropertySources();
        for (PropertySource propertySource : propertySources) {
            if (propertySource.getName().contains("applicationConfig: [classpath:/bootstrap")) {
                configurableEnvironment.getPropertySources().addBefore(propertySource.getName(), new MapPropertySource(name, map));
                break;
            }
        }
    }

上述代碼中，就將自定義的配置文件優先級加載到bootstrap配置文件優先級之前；所以bootstrap<自定義<application

同理可舉一反三