Sign other types of artifacts about chains HOT 19 CLOSED

Two that immediately come to mind are PipelineRuns as well as Runs (for custom tasks cc @imjasonh).

It might also be prudent to better formalize the way image outputs are signed. I was spitballing this with @dlorenc a week or so ago, but this would be another great application of duck typing task/pipeline[1] input/output shapes (as I was playing with in mattmoor/mink motivated by CLI DevX).

[1] - From here on I'm going to say "task" when I really mean task, pipeline, or a user-defined custom task definition.

The general idea is that tooling (including some possible defined by Tekton upstream) would standardize around certain task signature "shapes". Imagine if tasks with outputs named like dev.tekton.imagedigest.* (strawman) could be interpreted as being image digest outputs?

These duck types aren't semantically meaningful to tekton/pipeline itself (like say pipeline resources were), but enable an extensibility model that puts the burden of adhering to such conventions on consuming tools (e.g. tkn, dashboard, chains).

Another aspect of wanting standardization of certain conventions is that we can start to make the catalog adhere to them so that folks can get a really nice OOTB experience.

from chains.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

from chains.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

from chains.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

from chains.

@tekton-robot: Closing this issue.

from chains.

/reopen
/remove-lifecycle rotten

from chains.

@priyawadhwa: Reopened this issue.

from chains.

/area s3c

from chains.

TEP-84 is related to signing of PipelineRuns.

from chains.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

from chains.

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

from chains.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

from chains.

@tekton-robot: Closing this issue.

from chains.

I think this might be being covered by the TEP-0109 structured results work by @ywluogg ?

/reopen

from chains.

@bobcatfish: Reopened this issue.

from chains.

Yeah I think if the binaries and the files captured in Intoto attestation can be signed by TEP 109

from chains.

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen with a justification.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/close

Send feedback to tektoncd/plumbing.

from chains.

@tekton-robot: Closing this issue.

from chains.

For anyone looking for this functionality, the place it is currently documented is https://github.com/tektoncd/chains/blob/main/docs/intoto.md#structured-result-type-hinting

from chains.