Hierarchical configuration and property placeholders with jdbc backend

Description:

Consider following configuration hierarchy which I have for my cloud config server:

• application.properties
  • [directory] dev <-- environment dev
    • application-dev.properties
    • [directory] microservice-1 <--- microservice
      • microservice-dev.properties
  • [directory] qa <-- environment qa
    • application-qa.properties
    • [directory] microservice-1 <--- microservice
      • microservice-qa.properties

I have the flexibility of having property placeholders and common configuration with the above hierarchy
Example :

1. application.properties : has common configuration across the microservices for all environments.
2. application-dev.properties : has common configuration across microservices for dev environment.
3. microservice-dev : has specific configuration for microservice for dev environment

In case of override of properties with same key the service specific values are resolved.
Also it is possible to have placeholders to have values from other keys.

Question/Enhancement:
Usually the searchPaths configuration in spring.cloud.config is used to do this when the backend is git.
I would like to achieve the same thing using Jdbc backend, But seems like it is currently not possible.
Is there a workaround or is this already in future scope ?

The issue describes hierarchical configuration, property placeholders, and searchPaths behavior for a JDBC backend, but names no source files, tests, or entry points. Start by locating the JDBC backend configuration-loading code and existing searchPaths behavior; done would require a defined approach and tests covering hierarchy, overrides, and placeholder resolution.