Comments (19)
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.
In response to this:
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.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
from chains.
/reopen
/remove-lifecycle rotten
from chains.
@priyawadhwa: Reopened this issue.
In response to this:
/reopen
/remove-lifecycle rotten
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
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.
In response to this:
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.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
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.
In response to this:
I think this might be being covered by the TEP-0109 structured results work by @ywluogg ?
/reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
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.
In response to this:
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.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
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.
Related Issues (20)
- Remove TaskRunResults from `slsa/v2alpha1` HOT 10
- Mark `metadata.completeness.parameters` as `True` for `slsa/v2alpha1` task run level provenance HOT 5
- Chains v1.0.0 HOT 8
- Call for a doc on how to use Pipelines with Chains HOT 7
- artifacts.oci.signer supported values HOT 6
- Chains should caution users when configuring it to sign an artifact that it didn't produce
- migration from `PodSecurityPolicy` to `PodSecurityAdmission`? HOT 5
- Implementation of SLSA v1.0 predicate in Chains HOT 3
- Unable to sign image with kaniko when using --no-push arg HOT 2
- Cleanup Materials usage HOT 4
- Support new predicate type for pipelineRun resource HOT 12
- Add support for adding spec of on-cluster pipelines into SLSA v1.0 provenance HOT 8
- Add task results to SLSA 1.0 predicate for pipeline runs HOT 3
- Update buildType in SLSAV1.0 provenance HOT 4
- internalParameters update in SLSAv1.0 provenance HOT 5
- Add resolved top-level build config yaml to external parameters HOT 11
- Enhancement on Pipeline level provenance HOT 12
- storage/gcs: PipelineRun support HOT 2
- Chains adds `chains.tekton.dev/signed=true` annotation even if no keys supplied HOT 10
- Tekton-specialized buildType for SLSAv1.0 predicate HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chains.