Uploaded image for project: 'Connectivity Link'
  1. Connectivity Link
  2. CONNLINK-596

Dev Portal Experience for RHCL in Red Hat Developer Hub

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Critical Critical
    • 1.3.0
    • 1.3.0
    • None
    • None
    • RHCL Developer Hub Plugin (Dev Preview)
    • False
    • Hide

      None

      Show
      None
    • False
    • In Progress
    • 0% To Do, 67% In Progress, 33% Done

      Objective [Description]

      The objective here is to build a customizable, easy to use API Portal (Dev Hub) for developers to look through available APIs, links to docs, test endpoint availability & register new APIs for their applications through Developer Hub Plugin

       

      Key Requirements:

      • Simple Setup, Easy to Deploy & Authenticate
      • Secure & able to adhere to RBAC Policies
      • Capable of being branded to any organizations brand standards
      • We need to enable appropriate workflows that allow for self-service within the portal
      • (Not Necessary in v1) Consider how we can surface analytics on the developer portal via dashboards, graphics, etc.
      • (Not Necessary in v1) Ideally works in a multi-cluster context

       

      Use Case (App Dev):

      Jane Doe is the Application Developer for a very large banking organization (10,000+ employees). Jane & her team have been working on a banking application that provides all kinds of features/services available through her bank. Jane recently got tasked with registering this new banking application in the developer portal, set it up, test the services availability through the portal & provide the appropriate documentation on how to use the APIs. In order to scale to the number of teams/applications in the organization Jane needs the ability to handle registration (herself & her application), Once registered she needs to:

      • Test/validate within the portal that the service is reachable
      • Appropriate authentication mechanisms are in place to make a number of types of API calls (GET/PUT/DELETE/etc.)
      • Add instructions, documentation, links to documentation, etc. to each registered API
      • Lastly, validate metrics that are being surfaced for a varying array of request response type (200/300/400/500)

      Time Line

      • Developer Preview: February 2026
      • Tech Preview: June 2026
      • GA: October 2026

      Out of Scope

      • Full User Management
      • Non-Authenticated (External) Dev Portal - To be in following release(s)

              jmadigan@redhat.com Jason Madigan
              rh-ee-cferreir Christopher Ferreira
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: