Adding YAML support for configuration customization

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Adding YAML support for configuration customization

Emmanuel Hugonnet
Hello,
I've written a proposal [1] to support YAML configuration files in addition to the current XML configuration files.
Those YAML files wouldn't replace the XML files but could be used to customize a configuration: allowing to add or remove resources,
undefine or redefine attributes.
This configuration would be added on top of the existing XML configuration on boot but wouldn't impact the XML itself (as we would be in
'read-only' mode).
I have currently a PoC with a simple YAML example, and a cost of ~100 ms on boot time, most of it due to the YAML parsing.
Note that I want to leave some resources out of the scope of that feature: adding extension or subystem would be out of the scope since this
should be done at provisioning.
Thanks for your feedback.
Emmanuel

[1]: https://github.com/wildfly/wildfly-proposals/pull/384
_______________________________________________
wildfly-dev mailing list -- [hidden email]
To unsubscribe send an email to [hidden email]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s