Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10355

Ensure GET /conversatons/{conversation_id} endpoint is compatible with RHDH Lightspeed

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • 1.8.0
    • None
    • None
    • None
    • DEVAI Sprint 3278, DEVAI Sprint 3279, DEVAI Sprint 3281

      Story (Required)

      The GET /conversatons/{conversation_id} endpoint needs to be migrated to use llama stack to lightspeed-core, with feature parity of road-core

      Background (Required)

      The endpoint is to get a conversation history for a given user.

       

      The migration has been done: https://github.com/lightspeed-core/lightspeed-stack/blob/main/src/app/endpoints/conversations.py

       

      this issue is to ensure is compatible with RHDH Lightspeed, and make changes to LCore accordingly if required

      for any changes being made, unit tests, integration tests and documentation should also be part of this issue

       

       

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

              yangcao Stephanie Cao
              yangcao Stephanie Cao
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: