Inconsistent binding from environment varaibles to maps

I’ve noticed an inconsistency in properties binding from an ENV variable and property defined in application.properties

Consider following example:

@ConfigurationProperties("com.test")
public class Props {
    private Map<String, Map<String, String>> property;
}

application.properties <- binding works correctly

com.test.property.foo.bar=value

Environment variable <- binding fails

export COM_TEST_PROPERTY_CCC_DDD=VALUE

I would expect that the same binding behavior for an externalized configuration. Any idea how to resolve this issue using Spring Boot 1.5.2?

---

I am using Spring Boot 1.5.2, Linux Mint 18.1, Java 8 (“1.8.0_121”) Demo application available: https://github.com/peterjurkovic/spring-boot-binding-demo

[mkucharek]

I’ve just hit a similar issue with Eureka default zone with Spring Boot 2.0.0.M7 - it doesn’t seem to correctly handle camel cases when binding map elements…

[dturanski]

@philwebb This is a great test case: compound prefix with nested maps. If 2.0 can bind this correctly it can likely handle anything.