ASF GitHub Bot logged work on KNOX-2226:

                Author: ASF GitHub Bot
            Created on: 14/Feb/20 08:32
            Start Date: 14/Feb/20 08:32
    Worklog Time Spent: 10m 
      Work Description: smolnar82 commented on issue #263: KNOX-2226 - Add home 
page to Knox
URL: https://github.com/apache/knox/pull/263#issuecomment-586152593
   @risdenk ,
   WRT your JSON question: on one hand, you are right, it'd be cleaner when 
reading the JSON as you recommended. On the other hand, this API generates XML 
output too, and in that case, the current structure is cleaner IMO:
               <description>The Druid Coordinator exposes a web GUI for 
displaying cluster information and rule configuration.</description>
               <shortDesc>Druid Coordinator Console</shortDesc>
               <description>The Overlord provides a UI for managing tasks and 
               <shortDesc>Druid Overlord Console</shortDesc>
               <description>Hue UI is a Web interface for analyzing data with 
Apache Hadoop</description>
               <shortDesc>Hue UI</shortDesc>
   Moreover, the current solution is consistent with Admin API outputs:
   $ curl -iku admin:admin-password -H "Accept: application/json" 
   HTTP/1.1 200 OK
   Date: Fri, 14 Feb 2020 08:26:44 GMT
   Set-Cookie: KNOXSESSIONID=node01wffn263vit5nemdc9021f45z3.node0; 
Path=/gateway/admin; Secure; HttpOnly
   Expires: Thu, 01 Jan 1970 00:00:00 GMT
   Set-Cookie: rememberMe=deleteMe; Path=/gateway/admin; Max-Age=0; 
Expires=Thu, 13-Feb-2020 08:26:44 GMT
   Content-Type: application/json
   Content-Length: 1160
   Server: Jetty(9.4.26.v20200117)
      "topologies" : {
         "topology" : [ {
            "name" : "admin",
            "timestamp" : "1581667994000",
            "uri" : "https://localhost:8443/gateway/admin";,
            "href" : 
         }, {
            "name" : "cdp-proxy",
            "timestamp" : "1581625805000",
            "uri" : "https://localhost:8443/gateway/cdp-proxy";,
            "href" : 
         }, {
            "name" : "knoxsso",
            "timestamp" : "1581625577000",
            "uri" : "https://localhost:8443/gateway/knoxsso";,
            "href" : 
         }, {
            "name" : "manager",
            "timestamp" : "1581667994000",
            "uri" : "https://localhost:8443/gateway/manager";,
            "href" : 
         }, {
            "name" : "sandbox",
            "timestamp" : "1581625577000",
            "uri" : "https://localhost:8443/gateway/sandbox";,
            "href" : 
         } ]
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:

Issue Time Tracking

    Worklog Id:     (was: 387211)
    Time Spent: 5h 40m  (was: 5.5h)

> Add home page to Knox
> ---------------------
>                 Key: KNOX-2226
>                 URL: https://issues.apache.org/jira/browse/KNOX-2226
>             Project: Apache Knox
>          Issue Type: New Feature
>          Components: AdminUI
>    Affects Versions: 1.3.0
>            Reporter: Sandor Molnar
>            Assignee: Sandor Molnar
>            Priority: Major
>              Labels: UI
>             Fix For: 1.4.0
>         Attachments: OnePager-Apache_Knox_Home_Page.pdf
>          Time Spent: 5h 40m
>  Remaining Estimate: 0h
> The lack of a home or landing page for Knox leaves users without a well-known 
> place to discover the URLs for the various UIs and APIs that are being 
> exposed for access by the gateway.
> This results in the need for QuickLinks in management applications like 
> Ambari and Cloudera Manager to be rewritten to express the proxied URLs. This 
> also results in the need for users to have to continue to go to these 
> management applications for end-user URLs which is often not even appropriate.
> This proposal is for adding a Home page to Apache Knox which will present the 
> various URLs in ways that are intuitive for being able to consume the proxied 
> resources.

This message was sent by Atlassian Jira

Reply via email to