Repository navigation
Add option to ignore unresolvable nested placeholders - #3311
tallyblue123 wants to merge 2 commits into
Conversation
Signed-off-by: bigfacekitty <bigface.kitty@outlook.com>
|
Can you elaborate on the situations where this is needed? |
Hi. This is mainly needed for large legacy deployments. After upgrading Spring Cloud Config Server, requests for configuration files containing unresolvable nested placeholders may fail. In some projects, there are too many existing configuration files to update them all immediately. This opt-in switch provides a backward-compatible migration path by allowing such placeholders without failing the entire configuration request. |
|
What versions are you observing the incompatibility in? |
We have observed this behavior in 5.0.5. Based on our investigation, it appears to have been introduced in 4.4.4. We currently rely on a workaround to keep our legacy configurations working. |
|
What are the exact versions of the client and server? |
We are using Spring Cloud Config Server 5.0.5. No Config Client is involved, as the issue can be reproduced by sending an HTTP request directly to the server. |
Signed-off-by: bigfacekitty <bigface.kitty@outlook.com>
09c1a20 to
6c18768
Compare
This branch has not been deployed
4 participants
This change improves compatibility when upgrading Config Server for projects with many legacy configuration files containing unresolved nested placeholders.