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

同理可举一反三