[KNOX-2265] Cloudera Manager discovery - check configs by their related names

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0
• Fix Version/s: 1.4.0
• Component/s: cm-discovery
• Assignee: Sandor Molnar
• Reporter: J.Andreina
• Created: 06/Mar/20 08:47
• Updated: 21/Apr/20 14:52
• Resolved: 06/Mar/20 17:36

Description

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 

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
    } 

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.: [e-mail]

Issue Links

• links to: GitHub Pull Request #280