[jira] [Created] (KNOX-2265) Cloudera Manager discovery - check configs by their related names

["Sandor Molnar (Jira)" <ji...@apache.org>]

Sandor Molnar created KNOX-2265:
-----------------------------------

             Summary: Cloudera Manager discovery - check configs by their related names
                 Key: KNOX-2265
                 URL: https://issues.apache.org/jira/browse/KNOX-2265
             Project: Apache Knox
          Issue Type: Bug
          Components: cm-discovery
    Affects Versions: 1.4.0
            Reporter: Sandor Molnar
            Assignee: Sandor Molnar
             Fix For: 1.4.0


Cloudera Manager provided configurations (service and role configs) have two unique identifiers:
 * name
 * related name

As of now, during service discovery, Knox only checks for the first one. However, it's perfectly fine if a particular service model identifies a configuration with the corresponding related name.

For instance, at the time of this Jira being filed, Hive Server 2 tries to identify the schema using {{hive.server2.use.SSL}} from 
{code:java}
class ApiConfig {
        name: hiveserver2_enable_ssl
        value: true
        required: false
        _default: false
        displayName: Enable TLS/SSL for HiveServer2
        description: Encrypt communication between clients and HiveServer2 using Transport Layer Security (TLS) (formerly known as Secure Socket Layer (SSL)).
        relatedName: hive.server2.use.SSL
        sensitive: false
        validationState: OK
        validationMessage: null
        validationWarningsSuppressed: null
    } {code}
As this sample shows, this particular configuration's name is {{hiveserver2_enable_ssl}} so that the discovery process will always default to {{http}} as the scheme.

 

Cc.: [~pzampino@apache.org]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)