spring-cloud-config: Properties not resolved on FactoryBean initialization

I’ve been using the Spring Cloud Config Client to connect to a config server on PCF. Unfortunately I’m using some legacy code that loads a keystore in an afterPropertiesSet of an InitializeBean, which is also a FactoryBean.

I noticed that when using the Config Client, the properties are not resolved even when they’re available in an application.properties. Strange thing is that one of the properties, location of type Resource is resolved.

My question is: Is this expected behavior and am I just missing something, or should all the properties be available when the bean is initialized? I’m guessing the latter so it seems like a bug to me and that’s why I’m submitting it here.

Here’s a link to a demo project illustrating the behavior: https://github.com/D0rmouse/spring-cloud-config-1167

You’ll see the following output when running the application:

Location: class path resource [somekeystore.jks]
Password: [$, {, s, s, l, ., k, e, y, s, t, o, r, e, ., p, a, s, s, w, o, r, d, }]
Type: ${ssl.keystore.type}

After removing the spring-cloud-starter-config dependency and running again the output will be:

Location: class path resource [somekeystore.jks]
Password: [c, h, a, n, g, e, i, t]
Type: jks

I would expect both outputs to be the same.