When a config-server is configured with a composite of environment repositories, the CompositeEnvironmentBeanFactoryPostProcessor is registering each EnvironmentRepository with the application context but is not registering the associated EnvironmentRepositoryProperties. This is inconsistent with the behaviour of an individually configured (non-composite) environment repository.
This is causing an issue in Spring Cloud Services config-server when we're trying to refresh Vault tokens periodically. Once this refresh logic is accepted into spring-cloud-config (I believe there's a newish PR open) it will become a bug here too.