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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KNOX-2265?focusedWorklogId=399013&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-399013 ]

ASF GitHub Bot logged work on KNOX-2265:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Mar/20 09:31
            Start Date: 06/Mar/20 09:31
    Worklog Time Spent: 10m 
      Work Description: smolnar82 commented on pull request #280: KNOX-2265 - Checking CM configs by their related names and read hive.server2.use.SSL from the service configuration
URL: https://github.com/apache/knox/pull/280
 
 
   ## What changes were proposed in this pull request?
   
   CM configuration's related name is used when looking up service/role configurations.
   Moreover, it turned out that `hive.server2.use.SSL` is a service configuration rather than being a role configuration.
   
   ## How was this patch tested?
   
   Updated and ran JUnit tests and tested manually:
   
   1. had a secure remote cluster (i.e. SSL enabled) with Hive/Hive on TEZ
   2. redeployed Knox locally and added a descriptor with HIVE
   3. set the remote cluster's attributes in this descriptor's `Service Discovery` details
   4. confirmed that
     - service discovery worked
     - Hive URLs start with the `https` scheme
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 399013)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>            Priority: Major
>             Fix For: 1.4.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)