apache
seata2.5配置文件加载顺序有问题，导致SpringBootConfigurationProvider#getConfigFromEnvironment无法正常加载到配置
Check Ahead
-
[x] I have searched the issues of this repository and believe that this is not a duplicate.
-
[x] 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
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.
Hi @chenmuhu, thanks for opening the issue! I tried reproducing it based on your description and screenshot, but it didn’t happen on my side. Could you give a bit more info — maybe the exact steps, version, or environment setup you’re using?
By the way, feel free to add me on DingTalk(iwongjian666) if it’s convenient. I can then invite you to our developer group for easier communication.