[
https://issues.apache.org/jira/browse/KNOX-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Zampino updated KNOX-1914:
-------------------------------
Description:
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.
was:
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 reasons:
# Subsequent additional discovery providers implemented in Knox won't require
further Admin UI changes.
# User/Customer discovery provider extensions would get Admin UI support
automatically.
> 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
> 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
(v7.6.3#76005)
