[
https://issues.apache.org/jira/browse/KNOX-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831641#comment-16831641
]
ASF subversion and git services commented on KNOX-1855:
-------------------------------------------------------
Commit 95f8c8f8a35b17976b567dffb0dbe8bfa60db7d4 in knox's branch
refs/heads/master from jtran-cloudera
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=95f8c8f ]
KNOX-1855 - Add Service Definition for Cloudera Manager API (#88)
This commit adds a basic service definition for Cloudera Manager that supports
the CM API.
Testing:
* Manual testing via curl and Python API bindings
* ant verify
> Add Service Definition for Cloudera Manager API
> -----------------------------------------------
>
> Key: KNOX-1855
> URL: https://issues.apache.org/jira/browse/KNOX-1855
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 1.2.0
> Reporter: Johnny Tran
> Priority: Major
> Fix For: 1.3.0
>
> Attachments: KNOX-1855.patch
>
> Time Spent: 1.5h
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
