Closed kabennett closed 4 years ago
We upgraded our dependencies to Spring Boot 2.3.2.RELEASE and Spring Cloud Hoxton.SR8, and this issue still remains. Our @ConfigurationProperties objects are still not binding at application startup and return null values when we try to instantiate AWS beans. Is this a known issue and/or is there a current workaround that has been identified until this issue is fixed?
Thanks for reporting and apologies for inconvenience. Fix is on the way.
Working versions Spring Boot: 2.2.9.RELEASE, Spring Cloud: Hoxton.SR6 Spring Boot: 2.2.9.RELEASE, Spring Cloud: Hoxton.SR7, Spring Cloud AWS dependency overrides to revert to 2.2.2.RELEASE
Failing versions Spring Boot: 2.2.9.RELEASE, Spring Cloud: Hoxton.SR7 Spring Boot: 2.2.9.RELEASE, Spring Cloud: Hoxton.SR6, Spring Cloud AWS dependency overrides to upgrade to 2.2.3.RELEASE
When our Spring Boot microservice starts in our local environment with LocalStack running, we see the following stack trace in our logs:
Immediately after this, when the
localStackProperties
object is referenced within thelocalAmazonS3
method below, we are encounteringNullPointerException
s.@ConfigurationProperties
are never bound from our YML property files in Git via Spring Cloud Config after we see the above stack trace in our logs.