<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 3, 2016 at 11:58 AM, Juraci Paixão Kröhling <span dir="ltr"><<a href="mailto:jpkroehling@redhat.com" target="_blank">jpkroehling@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 03.02.2016 11:44, Thomas Heute wrote:<br>
> What am I missing ?<br>
<br></span>
Tooling support. Using an external properties file would require tools that are already compatible with Wildfly to make adaptations to support Hawkular.<br>
<br>
I'm not sure which one is better, though: to allow admins to change Hawkular properties via tools they use for managing Wildfly (via CLI? Admin console?), or to externalize it all in a "hawkular.properties" file, which can also be easily managed via ansible/puppet/chef.<br></blockquote><div><br></div><div>IMO going to Wildfly management tools to configure Hawkular is IMO not a great experience. </div><div><br></div><div>IMO for Hawkular users, Wildfly is an internal detail and its complexity should be relatively hidden.</div><div><br></div><div>Thomas</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
- Juca.<br>
<br>
</blockquote></div><br></div></div>