Story (Required)

As a user trying to describe the pipelineruns using opc, I want to describe the pipelinesruns created by the results

Background (Required)

<Describes the context or background related to this story>

Uptil now user can only describe the pipelineruns present in cluster but there is a usecase to describe pipelineruns created by the 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>

opc pipelineruns describe command should be able to describe the pipelineruns from the cluster and 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 describe => should describe the pipeline runs in the results and the cluster

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