seata2.5配置文件加载顺序有问题，导致SpringBootConfigurationProvider#getConfigFromEnvironment无法正常加载到配置

[chenmuhu]

Check Ahead

• I have searched the issues of this repository and believe that this is not a duplicate.

• I am willing to try to fix this bug myself.

Ⅰ. Issue Description

2.3的是先加载application.properties文件再去加载seata.config.type配置的，正常

2.5的没有加载到就去加载seata.config.type配置了，导致无法正常加载

Ⅱ. Describe what happened

No response

Ⅲ. Describe what you expected to happen

No response

Ⅳ. How to reproduce it (as minimally and precisely as possible)

No response

Ⅴ. Anything else we need to know?

No response

Ⅵ. Environment

No response

[funky-eyes]

This issue seems to occur only in Spring Cloud applications; plain Spring Boot applications behave normally. A temporary workaround is to put the configuration in bootstrap.yml. To fix it properly, we need to investigate why, starting with Seata version 2.3, some Seata beans are being loaded with higher priority.

[WangzJi]

Hi @funky-eyes, I’d like to take this.