Epic Goal

• RAG advanced support in RHDH  Lightspeed
• This issue includes:
  • Link RAG to RHDH documentation
    • Should we add tech docs from plug ins that we've prebuilt?
    • RAG data should not be part of base image, it should be mounted to a volume storage
  • backend API which act as a proxy for frontend to interact with the road-core RAG API

Why is this important?

• ...

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

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