[
https://issues.apache.org/jira/browse/KNOX-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935895#comment-16935895
]
ASF subversion and git services commented on KNOX-1914:
-------------------------------------------------------
Commit 51b9ab77960eeb1a65248ac2f602d7903765ac82 in knox's branch
refs/heads/master from Sandor Molnar
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=51b9ab7 ]
KNOX-1914 - New admin API to be used by the UI to fetch available service
discovery types (#147)
> 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
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> 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.4#803005)
