[
https://issues.apache.org/jira/browse/AMBARI-15843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrii Babiichuk updated AMBARI-15843:
--------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
committed to trunk
> Adding Test Connection widget to a theme for custom service requires JS change
> ------------------------------------------------------------------------------
>
> Key: AMBARI-15843
> URL: https://issues.apache.org/jira/browse/AMBARI-15843
> Project: Ambari
> Issue Type: Task
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Fix For: 2.4.0
>
> Attachments: AMBARI-15843.patch
>
>
> We have the information of Ranger KMS servers hosts in App.Hostcomponent
> model if the cluster is installed. If not then its available in the
> localstorage.
> It will be good to change the logic so that the source host while testing
> connection is not derived from property but it is derived from component
> name. If theme definition can have SOURCE_HOST = RANGER_KMS_SERVER, then UI
> code should be able to do the test connection action without demanding a
> property like "ranger_kms_server_hosts" to be available in the stack
> definition
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)