[ https://issues.redhat.com/browse/WFLY-13779?page=com.atlassian.jira.plugi... ] Jeff Mesnil commented on WFLY-13779: ------------------------------------ I have thought about this more. The main thing to consider is that with MicroProfile Config, the config sources are added to the Config the first time a class loader calls ConfigProviderResolver.getConfig(). Any addition/removal of a config-source provided by the subsystem will not modify existing Config associated to a ClassLoader. In case of deployments, that means that the set of ConfigSources is determined when the deployment is deployed. For WildFly subsystems, that means that the set of ConfigSources is determined when the use MicroProfile Config the first time. Any subsequent modifications to the microprofile-config-smallrye substem will not impact these Configs. So I think we need to make 2 changes: * in the WildFly codebase, flag the config-source and config-source-provider :remove operations with RESTART-ALL-SERVICES to properly notify that if these resources are removed, server must be reloaded * in your test fixture, after removing a config-source-provider, you'll have to reload the server to get it in the proper state. -- This message was sent by Atlassian Jira (v7.13.8#713008)