Story (Required)

As a developer trying to use Pipelines as Code for my CI I want Pipelines as Code to let me know that my PipelineRun or TaskRun has an invalid specification so that I can correct it during a pull request or after code merges.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

User-provided YAML must pass the Pipeline validation webhooks, which may not be intuitive to users that are experiencing Tekton and Kubernetes for the first time.
Things like the "DNS Label" constraint for task and pipeline names may come as a surprise.

See for a real world experience via StoneSoup: https://redhat-internal.slack.com/archives/C02CTEB3MMF/p1678467580810049?thread_ts=1678464332.887079&cid=C02CTEB3MMF

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

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>

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