In both cases the Consul paths should point to an actual key/value and not to a folder in the store
Requirements
Implement a capability to provide a list of Consul KV store folders in the application config, then recursively scan those folders for sub-folders and build config properties from the key/values found.
Build the key of the property as a concatenation of the full path in Consul KV, minus the value of quarkus.consul-config.prefix.
Background
At the moment an application developer load the configuration from Consul's Key Value store using the Quarkus consul-config extension.
You can either obtain a single config property from a list of Consul key/values via:
Or you can load a bunch config properties from a Consul key/value that is laid out as a properties file via:
In both cases the Consul paths should point to an actual key/value and not to a folder in the store
Requirements
Implement a capability to provide a list of Consul KV store folders in the application config, then recursively scan those folders for sub-folders and build config properties from the key/values found.
Build the key of the property as a concatenation of the full path in Consul KV, minus the value of
quarkus.consul-config.prefix
.Provide only support for raw values.