• Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • DEVAI Sprint 3263

      Story (Required)

      API for UI  to delete the chat session

      see design doc for /session/delete: https://docs.google.com/document/d/1nzW-crxBZoayWDWlZbtk0q6bmWFPy9qJ8Yun_zNOvRk/edit#heading=h.b5q4khsxygm4

       

       

      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

       

      This issue also will includes test automation for the new API

      Background (Required)

      <Describes the context or background related to this story>

      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.>

       

      requires https://issues.redhat.com/browse/DEVHAS-756 to be done

       

      for https://issues.redhat.com/browse/DEVHAS-757 & https://issues.redhat.com/browse/DEVHAS-761 , need to delete the chat history for that session.

      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

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

                Created:
                Updated:
                Resolved: