Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/1275
I'm not sure if we can have Ambari do that in a general way. Right now we
do have the Metron client get distributed throughout for the purpose of setting
up Storm security. We could also do the same thing for whatever we need to
distribute for Knox. It means a Metron Client needs to coexist with any Knox
servers, but that seems like a reasonable restriction (even if I'd rather not
have to deal with it). I think that would also address the custom topology
question.
If we're okay with putting more load on the Metron Client, I'd rather use
the custom topology and just do it that way.
For quicklinks, I'm okay with having the manual update process documented
as part of the Knox setup, as long as it's noted its not a Metron issue, it's
an Ambari/Knox interaction issue (and maybe just link to the Jira)
---
