[ 
https://issues.apache.org/jira/browse/KNOX-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235036#comment-16235036
 ] 

Phil Zampino commented on KNOX-1013:
------------------------------------

[~lmc...@apache.org] I don't anticipate having a patch for this that quickly, 
so I would recommend moving it out.

Refreshing would involve triggering the discovery mechanism for each 
descriptor; Manually, it's as simple as touching the descriptor or a referenced 
provider configuration.

> Monitor Ambari for Cluster Topology changes
> -------------------------------------------
>
>                 Key: KNOX-1013
>                 URL: https://issues.apache.org/jira/browse/KNOX-1013
>             Project: Apache Knox
>          Issue Type: Sub-task
>          Components: Server
>            Reporter: Phil Zampino
>            Assignee: Phil Zampino
>            Priority: Major
>              Labels: kip-8
>             Fix For: 0.14.0
>
>
> Knox should provide the option to monitor an Ambari cluster for which it has 
> deployed a topology, in order to notice configuration changes that affect the 
> service URLs for that topology. Upon noticing such a change, Knox should 
> respond by updating the deployed topology appropriately.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to