Chitrang Patel
Chitrang Patel
Like we do for remote specs (remote pipelines/tasks), we could put the local (not-embedded) pipeline and task specs into `resolved Dependencies` since each `resolved dependency` is [a resource descriptor](https://github.com/in-toto/attestation/blob/main/spec/v1/resource_descriptor.md) to...
## Summary For now, we will add a checksum of the input spec into the provenance instead of base64 encoded content. This makes it consistent with remote resources. We may...
Added support for generating the hash of the object in the status: https://github.com/tektoncd/pipeline/pull/6964 Once released, Tekton chains will be able to populate it directly.
Follow up in Issue https://github.com/tektoncd/pipeline/issues/6593
Marking this as done since https://github.com/tektoncd/pipeline/issues/6593 made it configurable
I wanted to raise this discussion again since at this point, Chains e2e tests only run with very old versions of Tekton Pipelines. It is challenging to test against newer...
Yes, I agree with that sentence. So the idea is that we don't want `pipelineRun` to inherit anything. It should be explicitly declared there and passed on to the layers...
Today, if you look at https://github.com/tektoncd/chains/issues/1117, I think that the issue is that even within a standalone TaskRun, we zap the annotation completely. Isn't that wrong? I think the issue...
/ok-to-test