You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2019/05/02 13:52:00 UTC

[jira] [Resolved] (KNOX-1855) Add Service Definition for Cloudera Manager API

     [ https://issues.apache.org/jira/browse/KNOX-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Risden resolved KNOX-1855.
--------------------------------
    Resolution: Fixed

> Add Service Definition for Cloudera Manager API
> -----------------------------------------------
>
>                 Key: KNOX-1855
>                 URL: https://issues.apache.org/jira/browse/KNOX-1855
>             Project: Apache Knox
>          Issue Type: New Feature
>          Components: Server
>            Reporter: Johnny Tran
>            Assignee: Johnny Tran
>            Priority: Major
>             Fix For: 1.3.0
>
>         Attachments: KNOX-1855.patch
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> I would like to contribute a patch to add a service definition for the Cloudera Manager API.
> -Currently, the service definition relies on CM being deployed in its own topology and accessed without the gateway and topology in the request URL (e.g. "/api/v30/..." instead of "/gateway/sandbox/api/v30/..."). This is because we will soon add CM web UI rules to the CM service definition, and limitations in the CM web UI make it impractical for the web UI to deal with additional path components.-
>  
> Updated: The CM API rewrite rules will not require the above provisions to work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)