That's right, we needed that during installation so the ES properties could
be provided/replaced by Ambari. I was also thinking through the
implications of splitting out that type of configuration from the rest of
the global config. I hate to add yet another configuration file to the mix.
But maybe
Ambari has to manage the global configuration at least once or we cannot
deploy. IIRC, last time this came up, we decided to expose it via Ambari
but see if we could turn off the restart. I think we could expose it via an
action.
I'm pretty happy with any solution that takes that initial deploymen
I think this has been touched on before, but I've been doing some testing
with the MPack and new REST API and Management UI and there are some things
I think we can make better. One of those items is the way we manage the
global config.
I think it would be beneficial to manage the global config th
