I'd like to be able to externalize my application configuration - using Microprofile config - as a properties file or yaml file. I'd like to be able to configure this file(s) by creating a "/subsystem=microprofile-config-smallrye/config-source" and then refers to a properties-file or a yaml file similar to what's possible in Quarkus (or Thorntail).

I'm fully aware that this is possible by creating a custom config source in my application. But I think as this kind of feature is/was provided in other RH products like Quarkus, wildly-swarm or thorntail customers will expect it to be available in wildfly/eap as well.

sample cli snippet:

/subsystem=microprofile-config-smallrye/config-source=application:add(properties-file=/config/application.properties)

I think the current alternatives in config-source are not really easy to use and far from what users expect from modern application runtimes.