Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-6470

Log Get API shouldn't do translation to GRPC.

XMLWordPrintable

    • Pipelines Sprint Crookshank 16

      Story (Required)

      Background (Required)

      At present, when we make get Log call. API server converts it to protobuff/GRPC, then receives a response from Loki, then converts to protobuff/GRPC, then JSON.

      This translation should be avoided. A native REST API endpoints should be there.

      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 (Mandatory)

      • Backward compatibility with existing API.
      • Update e2e tests to make Rest API call also.

      ***

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      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 etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              rh-ee-kbaig Khurram Baig
              rh-ee-kbaig Khurram Baig
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: