Story (Required)

As a user trying to list the pipelineruns, I want to see pipelinesruns created by the results

Background (Required)

<Describes the context or background related to this story>

Uptil now user can only see pipelineruns present in etcd but there is a usecase to show pipelineruns created by results

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>

By default opc pipelineruns list will show pipelineruns from etcd as well as from the results. There will be separate parameter to identify the pipelineruns from etc and from results.

There should also be a way where the user can filter the pipelines based on the cluster or from the results.

Dependencies

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

Acceptance Criteria (Mandatory)

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

opc pipelinrun list => should provide all lists of pipeline runs in the cluster both results and cluster

--cluster and --results flag can help to filter.

–cluster => shows only from cluster 

–results => shows only from results

In the cli output view we should add additional column to show whether a record belongs to cluster/results

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