Story (Required)

API for UI to access the chat session with the chat history

see design doc for /session/load: https://docs.google.com/document/d/1nzW-crxBZoayWDWlZbtk0q6bmWFPy9qJ8Yun_zNOvRk/edit

will need to verify userid passed in with the login user & token, the function will be done as part of: https://issues.redhat.com/browse/DEVAI-45

Background (Required)

<Describes the context or background related to this story>

at least requires https://issues.redhat.com/browse/DEVHAS-757 to be done

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 DEVHAS team only)
R&D label required (Filled by DEVHAS 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