Story (Required)

We need that in Tekton Pipeline and a PR was open to add that functionality to Pipeline and used by the controllers (https://github.com/tektoncd/pipeline/pull/9013). However this requires changes to some files which are otherwise auto generated from Knative code and there is no (known) flexibility to introduce changes to them. So as suggested in a discussion with the team, we are going to try and introduce that in Knative.

There seems to be very old issue about it and it does not look it got much traction https://github.com/knative/pkg/issues/2128. I'll try to follow up on it.

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

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