I've reviewed multiple possible options but every one of them is rather complicated. Instead, I've decided to create a new script (old kept for reference for now), UpdateConfig.groovy which allows the user to download current config, modify it and apply it to the server. Right now script works on single cluster node as clustering may be more difficult or even not possible if each cluster node would have a different config.

As I've checked this works ok with Kernel as it was designed to handle the change of the configuration. However, I cannot tell if this will work in all of the cases.

I suppose that a script like it is could be useful but is potentially dangerous as it may cause a crash and restart - but that can be caused even by scripts for previous versions of Tigase. I would say that we should not work on that anymore as we are working on reducing the​ number of settings kept in etc/config.tdsl.

Right now script works on single cluster node as clustering may be more difficult or even not possible if each cluster node would have a different config.

AFAIR we agreed that we should aim for all nodes having same configuration…

I would say that we should not work on that anymore as we are working on reducing the​ number of settings kept in etc/config.tdsl.

... and moving things to database (which would minimise/eliminate first issue). Thus I concur we can close this one and focus on moving more settings to database.