Uploaded image for project: 'apiman (API Management)'
  1. apiman (API Management)
  2. APIMAN-772

create a service explorer UI for services which may or may not have a policy/plan

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • 1.2.x
    • None
    • None
    • None

      While watching Kurt and Eric demo ApiMan at New York last week I loved the Swagger UI stuff and discover of services from Kubernetes.

      I'd love it if ApiMan replaced the old fabric8 api registry & UI view really; so that its the preferred UI to view/search/filter services inside Kubernetes (filtering by namespace, labels, text etc). Then for a given service when its chosen, we visualise as much metadata as we can find from the service itself (e.g. via annotation etc), show the Swagger, then show any current policies & plans; and make it then a 1 click to then create/edit the plans.

      So in general ApiMan becomes more of the generic "API Console" for kubernetes and the front end of the "Service Catalog" really

        1. screenshot-1.png
          92 kB
          Eric Wittmann
        2. Screenshot 2015-12-15 22.31.42.png
          100 kB
          Kurt Stam
        3. Screenshot 2015-12-15 22.31.56.png
          51 kB
          Kurt Stam

              ewittman@redhat.com Eric Wittmann
              jastrachan_jira James Strachan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: