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

Sandor Molnar commented on KNOX-1914:
-------------------------------------

[~pzampino] - I plan to implement a REST API which would return the following 
JSON object:
{code:java}
{
        "knoxServiceDiscoveryList": [
        {
            "type": "Ambari",
            "implementaion": 
"org.apache.knox.gateway.topology.discovery.ambari.AmbariServiceDiscovery",
            "test": "false"
        },
        {
            "type": "ClouderaManager",
            "implementaion": 
"org.apache.knox.gateway.topology.discovery.cm.ClouderaManagerServiceDiscovery",
            "test": "false"
        },
        {
            "type": "PROPERTIES_FILE",
            "implementaion": 
"org.apache.knox.gateway.topology.discovery.test.extension.PropertiesFileServiceDiscovery",
            "test": "true"      
        }
        ...
    ]
}
{code}
Once it's done I'd modify the admin UI to use this API and display the {{type}} 
field of a {{serviceDiscovery}} where the {{test}} flag is {{false}}. There 
would be some other minor refactoring in the code, but it's not a lot of work.

Any objection?

> Dynamic population of Admin UI service discovery type options
> -------------------------------------------------------------
>
>                 Key: KNOX-1914
>                 URL: https://issues.apache.org/jira/browse/KNOX-1914
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: AdminUI
>    Affects Versions: 1.3.0
>            Reporter: Phil Zampino
>            Assignee: Sandor Molnar
>            Priority: Major
>             Fix For: 1.4.0
>
>
> The Discovery Details section of the Admin UI for working with descriptors 
> includes a drop-down list of supported discovery providers (e.g., Ambari, 
> ClouderaManager). Currently, this list is statically defined in the Admin UI. 
> It should be possible to expose an API from the Knox host for determining the 
> list of supported discovery providers.
> This API could leverage the same Java service loader mechanism that is used 
> by the discovery runtime to load discovery providers.
> This would be nice for two closely-related reasons:
>  # Subsequent additional discovery providers implemented in the Knox project 
> itself won't require further Admin UI changes.
>  # User/Customer discovery provider extensions would get Admin UI support 
> automatically.
>  



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to