brenthdaniel
commented
4 years ago We talked this over a bit. Some people felt that this information is mostly provided by the REST config API, and wondered if there is really value in producing an XML formatted file.
The next step here might be to prototype this and get examples of what a unified configuration file would look like with all sources included, but we need to decide whether we think this is worth doing or not first.
We continue to receive requests for a utility to produce a single server.xml file that contains all sources of configuration.
In practice, this may be less useful than it seems. Going from the transformed configuration back to an XML file would likely give a result that looks nothing like the original. Given the vast array of configuration sources, some of which are mostly hidden from users, the end result could be somewhat overwhelming.
But, given the interest in this, it's probably worth considering what we can do here.
We could potentially make the results more worthwhile by excluding certain sources of configuration -- either by design, or by using options. For example, there could be options to include/exclude default configuration, variable replacement, metatype defaults, internal attributes, etc. Some things, like config admin configs that are created directly by components, should probably always be excluded.