Story (Required)

As a consumer of road-core as upstream. we would like to have the chat history stored & able to be retrieved in road-core

Background (Required)

<Describes the context or background related to this story>

see description in https://issues.redhat.com/browse/DEVAI-289

this is the implementation issue after the investigation https://issues.redhat.com/browse/DEVAI-289 is done.

migrate our current chat history design to road-core using python:

update road-core existing core which stores plain text to use Langchain object and store more information as we required, i.e. summary, timestamp, model name etc.

a get history API, similar to the one in current lightspeed-backend], is required to be implemented to get chat history of a given conversation_id

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Required)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

documentation updates (design docs, release notes etc)
demo needed
SOP required
education module update (Filled by DEVAI team only)
R&D label required (Filled by DEVAI team only)

Done Checklist

Code is completed, reviewed, documented and checked in
Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
Continuous Delivery pipeline(s) is able to proceed with new code included
Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
Acceptance criteria are met
If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well