Commits on Nov 10, 2022

1. Populate the *Run.Status.Provenance.ConfigSource field …

   Prior, remote `ResolutionRequest` CRD supports **recording** the source information
   in its Status that identifies where the remote resource came from.
   Similarly, `TaskRun/PipelineRun` CRD supports **receiving** the source information
   via a field in its status from remote ResolutionRequest. Specifically,
   this field named `ConfigSource` is a subfield of the `Provenance` field in status.
   
   In this PR, we are trying to pass the data from `ResolutionRequest` to pipeline
   reconciler so that the data can be captured in TaskRun/PipelineRun's `Status.Provenance.ConfigSource`.
   The implication of this change is that many functions' interface has been
   changed because we are passing this extra source data alongside the remote resoure.
   
   Note:
   - The `provenance` field in Run.status is behind a feature flag named `enable-provenance-in-status`
   , which was introduced in tektoncd#5670. The field will be populated iff
   the flag is set to `true`.
   - If a pipeline yaml is from remote place A, and the individual tasks
   are from other remote places, pipelinerun status will only record the source
   for the pipeline, and the individual taskrun status will record the
   source for the corresponding task.
   
   Related PRs/Issues:
   - tektoncd#5580
   - tektoncd#5551
   - tektoncd#5670
   - tektoncd#5522
   
   Signed-off-by: Chuang Wang <[email protected]>

   

   chuangw6 committed Nov 10, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for 55744ed
   • Browse repository at this point

   Copy the full SHA

   55744ed View commit details

   Browse the repository at this point in the history