Ryan Baxter
Ryan Baxter
Thanks for reporting this issue, @david0. After investigating, I believe this is an expected behavior based on how Spring Boot's property binding works. The issue is in Spring Boot's `Binder`...
It is not something Spring Cloud can address since it is behavior of the Binder in Spring Boot so if the behavior needs to change, the change needs to be...
Thanks for the additional thoughts @wilkinsona. I will reopen this issue, but to be honest it is not going to be a high priority for us at this time as...
Can you elaborate more on why you want this to work?
> So I am wondering why [TextEncryptorConfigBootstrapper.java#L67-L85](https://github.com/spring-cloud/spring-cloud-commons/blob/main/spring-cloud-context/src/main/java/org/springframework/cloud/bootstrap/TextEncryptorConfigBootstrapper.java#L67-L85) is needed to promote them? Honestly I am not sure. If we don't promote them with bootstrap enabled then, yes it looks like...
The other thing I was thinking about was adding a property so we disable promoting of the beans (it would be disabled by default) allowing your use case to work...
Please try and reproduce this using 2024.0.3 and if you can reproduce it please provide a sample that shows how to reproduce the issue.
Not sure. Maybe @spencergibb knows?
I don't think we would be against this, if you want to create a PR for it we would be happy to consider it.