@Sgitario I tried reviewing the PR but I am missing the context. It's not clear to me what you are trying to do and why.
Some rough examples:
Why do we need a clone step ?
We need a git clone step, because the PipelineResources of type git is removed in Tekton 0.47. For the migration, I did what was described in https://tekton.dev/docs/pipelines/resources/ which says to replace the pipelineresources to params and use the git-clone task (see the image).
Why in some areas are replacing ouput references for had coded values ?
As far as I see, there are no hard-coded values, but default values that users can modify if needed. I don't think this has changed by these changes. But before these properties were provided via resources inputs/outputs, and now via params.
Note, that I have't touched tekton for nearly two years now, so I am bit rusty.
We need a git clone step, because the PipelineResources of type git is removed in Tekton 0.47. For the migration, I did what was described in https://tekton.dev/docs/pipelines/resources/ which says to replace the pipelineresources to params and use the
git-clone
task (see the image).As far as I see, there are no hard-coded values, but default values that users can modify if needed. I don't think this has changed by these changes. But before these properties were provided via resources inputs/outputs, and now via params.