Affected versions Spring Boo version: 2.7.13 (same behaviour for 2.7.17) Spring cloud version: 2021.0.8
We have decided to replace our properties files with yaml files in config server. Properties are loaded in correct order 1. Local properties 2. Fetch properties from config server 3. Fetch properties (secrets) from AWS Parameter Store
The problem is that if the property exists in yaml files in config server repository and in SSM. The property values is not override based on values from AWS Parameter Store. The AWS Parameter Store has the highest precedence so it should always override the value. It has stopped working since we started using yaml files instead of *.properties files.
Apologise if I have chosen wrong place to report it
Comment From: wilkinsona
Spring Boot isn't aware of how properties are loaded in Config Server so it is unlikely to be a problem that we can fix here. I think this should be investigated by the Spring Cloud Config team so please open an issue with them. When you do so, please supply a minimal reproducible example.