Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Capture provenance of StepActions in Status #8091

Closed
chitrangpatel opened this issue Jul 3, 2024 · 1 comment · Fixed by #8106
Closed

Capture provenance of StepActions in Status #8091

chitrangpatel opened this issue Jul 3, 2024 · 1 comment · Fixed by #8106
Assignees
@chitrangpatel
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@chitrangpatel
Copy link
Contributor

chitrangpatel commented Jul 3, 2024 •
edited
Loading

Feature request

We need to record the provenance (uri and the digest) of the remote StepActions in the TaskRun's Status.

Use case

Issue #5550 enabled the surfacing of the provenance (i.e. uri and digest) of remote Pipelines and Tasks. 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.
@chitrangpatel chitrangpatel added the kind/feature Categorizes issue or PR as related to a new feature. label Jul 3, 2024
@chitrangpatel
Copy link
Contributor Author

cc @lcarva @renzodavid9 @wlynch @vdemeester

@chitrangpatel chitrangpatel self-assigned this Jul 5, 2024
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Jul 9, 2024
@chitrangpatel
Capture Remote StepAction Location in TaskRun Status
758f128 
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 chitrangpatel mentioned this issue Jul 9, 2024
Merged
8 tasks
chitrangpatel added a commit to chitrangpatel/pipeline that referenced this issue Jul 9, 2024
@chitrangpatel
Capture Remote StepAction Location in TaskRun Status
152fe38 
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
@chitrangpatel
Capture Remote StepAction Location in TaskRun Status
058d250 
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
@chitrangpatel
Capture Remote StepAction Location in TaskRun Status
3a78a4f 
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
@chitrangpatel @tekton-robot
Capture Remote StepAction Location in TaskRun Status
4e6baf9 
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
Assignees

@chitrangpatel chitrangpatel

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Capture Remote StepAction Location in TaskRun Status chitrangpatel/pipeline
1 participant
@chitrangpatel