-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Capture provenance of StepActions in Status #8091
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
Comments
chitrangpatel
added
the
kind/feature
Categorizes issue or PR as related to a new feature.
label
Jul 3, 2024
chitrangpatel
added a commit
to chitrangpatel/pipeline
that referenced
this issue
Jul 9, 2024
Prior to this, we captured remote Task and pipeline origin information (uri and digest) in the TaskRun/PipelineRun Status. This allowed Chains to pull this information and insert it into the intoto provenance. A similar capability was missing for the newly implemented StepActions. This PR fixes that gap. Fixes tektoncd#8091
8 tasks
chitrangpatel
added a commit
to chitrangpatel/pipeline
that referenced
this issue
Jul 9, 2024
Prior to this, we captured remote Task and pipeline origin information (uri and digest) in the TaskRun/PipelineRun Status. This allowed Chains to pull this information and insert it into the intoto provenance. A similar capability was missing for the newly implemented StepActions. This PR fixes that gap. Fixes tektoncd#8091
chitrangpatel
added a commit
to chitrangpatel/pipeline
that referenced
this issue
Jul 15, 2024
Prior to this, we captured remote Task and pipeline origin information (uri and digest) in the TaskRun/PipelineRun Status. This allowed Chains to pull this information and insert it into the intoto provenance. A similar capability was missing for the newly implemented StepActions. This PR fixes that gap. Fixes tektoncd#8091
chitrangpatel
added a commit
to chitrangpatel/pipeline
that referenced
this issue
Jul 18, 2024
Prior to this, we captured remote Task and pipeline origin information (uri and digest) in the TaskRun/PipelineRun Status. This allowed Chains to pull this information and insert it into the intoto provenance. A similar capability was missing for the newly implemented StepActions. This PR fixes that gap. Fixes tektoncd#8091
tekton-robot
pushed a commit
that referenced
this issue
Jul 19, 2024
Prior to this, we captured remote Task and pipeline origin information (uri and digest) in the TaskRun/PipelineRun Status. This allowed Chains to pull this information and insert it into the intoto provenance. A similar capability was missing for the newly implemented StepActions. This PR fixes that gap. Fixes #8091
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
We need to record the provenance (
uri
and thedigest
) of the remoteStepActions
in theTaskRun
'sStatus
.Use case
Issue #5550 enabled the surfacing of the provenance (i.e. uri and digest) of remote
Pipelines
andTasks
. This in turn allowed Tekton Chains to capture it in the intoto provenance.A corresponding capability is missing for remote
StepActions
and should be fixed. Without this information, the intoto provenance generated by Tekton Chains is incomplete.The text was updated successfully, but these errors were encountered: