Closed arewm closed 2 months ago
@arewm Can you give a concrete example of a workflow where not all parameters call me from Git?
@ifireball, This change would effectively loosen the requirements so that PAC is not required as a build trigger. If there were some system that wanted to leverage Konflux with its own method of orchestrating/triggering Tekton Pipelines then that is still acceptable as long as all parameters are recorded in the provenance.
@redhat-appstudio/book-publishers , are there any more discussions/thoughts around the suitability of this change for inclusion?
Semantic reproducibility should still be an architecture goal, but not all parameters will be reasonable to commit to the git repository. Instead of making this the goal, we should change the goal slightly to require the information to be represented in the provenance and then present in git where possible. This enables some workflows that leverage tekton but not PAC as still within-goal.