[
https://issues.apache.org/jira/browse/KNOX-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471437#comment-16471437
]
ASF subversion and git services commented on KNOX-1266:
-------------------------------------------------------
Commit 1d5eae8ee896e6eb7cc7b78beb9fd0fdf56dde39 in knox's branch
refs/heads/master from [~pzampino]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=1d5eae8 ]
KNOX-1266 - Employ gateway-site config for default discovery address and
cluster values
> Support aliases for default discovery address and cluster name
> --------------------------------------------------------------
>
> Key: KNOX-1266
> URL: https://issues.apache.org/jira/browse/KNOX-1266
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.1.0
> Reporter: Phil Zampino
> Assignee: Phil Zampino
> Priority: Minor
> Fix For: 1.1.0
>
>
> Currently, service discovery requires 4 pieces of information to interact
> with Ambari to generate topologies from descriptors:
> * discovery address
> * discovery cluster
> * discovery username
> * discovery password alias
> At present, there are 2 well-known aliases, which serve to provide defaults
> if the corresponding details aren't specified in a descriptor:
> * *ambari.discovery.user* - The value of this alias is the username for
> authenticating with the discovery source
> * *ambari.discovery.password* - The value of this alias is the password
> corresponding to the discovery user
> This issue suggests that Knox could support aliases as defaults for the
> remaining 2 discovery properties:
> * *ambari.discovery.address*
> * *ambari.discovery.cluster*
> This would make it easier for users who are defining multiple descriptors for
> the same cluster. The discovery details could be omitted from the
> descriptors, such that the defaults defined as aliases would be used.
>
> If these new aliases are defined, and the corresponding properties are not
> specified in a descriptor, the values of these aliases will be used as
> defaults.
> If either of these aliases is NOT defined, and is also unspecified in a
> descriptor, then discovery shall not be attempted.
> The Admin UI must also be addressed as part of this, since there is currently
> some validation to ensure that a sufficient amount of discovery information
> is specified in a new descriptor (if any is specified at all).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
