Epic Goal

Developer Lightspeed Service Endpoint & Core Behavior Configuration

As a Red Hat Developer Hub administrator, I need a dedicated panel to configure the essential connectivity and core behavior of the Developer Lightspeed service (ROADCore/LightspeedCore), ensuring secure and controlled access for our developers.

This feature streamlines the initial setup and ongoing operational control for Lightspeed within the Red Hat Developer Hub's administrative interface.

Goals (aka. expected user outcomes)

• Red Hat Developer Hub administrators can securely connect their Developer Hub instance to the correct Developer Lightspeed (ROADCore) backend service by configuring its endpoint URL and security key.

• Administrators can define the default Developer Lightspeed system prompt that guides the behavior of Developer Lightspeed interactions for all users.

• Administrators can control the enabling or disabling of the "Question Validation" feature for Lightspeed queries, enhancing content moderation or query refinement as needed.

• Administrators can control the enabling or disabling of the "Feedback" feature for Lightspeed queries, allowing them to choose choice if user feedback is sought and collected.
• The administrative panel for Developer Lightspeed configuration is securely accessible only to authorized Red Hat Developer Hub administrators through robust Role-Based Access Control (RBAC).

Why is this important?

This epic contains the backend work needed for this feature

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• For this to work, the ROADCore service must change to include the ability to return a list of selectable "models" as part of it's API. At the time of writing, this is a feature request for Lightspeed Core (LCORE-637)

• • Change the ROADCore/LightspeedCore API to return a list of models that the user can interact with.
    • Without this change, an extra configuration dependency exists - as it becomes necessary for Developer Lightspeed to communicate directly with the OpenAI API in order to present a list of models on screen to Developer Lightspeed users.
    • We may need to contribute this change to ROADCore, as upstream development has paused in favor of LightspeedCore.
      Once the above change to ROADCore/LightspeedCore is made, the requirements for the Developer Lightspeed configuration panel are as follows:

• • A new "Developer Lightspeed" configuration panel shall exist within the Red Hat Developer Hub's Administration section.
  • Access to this "Developer Lightspeed" administration panel shall be restricted to users holding the Red Hat Developer Hub administrator role, enforced through RBAC.
  • The panel shall provide an input field for administrators to set and persist the URL for the ROADCore/LightspeedCore service endpoint.
  • The panel shall provide a secure input field for administrators to set and persist the security key (e.g., API key or token) required for authenticating with the ROADCore service endpoint. This key must be stored securely.
  • The panel shall include a multi-line text input field allowing administrators to define the default "system prompt" that will be used for all Developer Lightspeed queries originating from Red Hat Developer Hub.
  • The panel shall include a clear toggle or checkbox option to enable or disable the "Question Validation" feature, indicating its current status.
  • All configuration changes made via this panel must be persisted and immediately applied to subsequent Developer Lightspeed interactions within Red Hat Developer Hub.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment