-
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
Remove deprecated TaskRun.Status.ResourceResults.ResourceRef
field
#4977
Remove deprecated TaskRun.Status.ResourceResults.ResourceRef
field
#4977
Conversation
cc @lbernick |
053579a
to
380f821
Compare
/assign @jerop @lbernick @pritidesai @vdemeester @afrittoli |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Andrew! Could you add a bit more context to the commit message and PR description (from the linked issue), stating that ResourceRef and ResourceName contain the same info but "resourceRef" doesn't make semantic sense? Also, you have a typo in the PR name (should be "deprecated")
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@abayer this was deprecated a long time ago and is overdue for removal, but wondering if we should send out an email to tekton-dev@ and tekton-users@ about the removal in the next release just in case someone is still using it and needs to migrate off it before the next release?
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop, lbernick The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
380f821
to
c518155
Compare
TaskRun.Status.ResourceResults.ResourceRef
fieldTaskRun.Status.ResourceResults.ResourceRef
field
See tektoncd#2694. The `TaskRun.Status.ResourceResults.ResourceRef` field was only ever used for its own `Name` field, and as part of tektoncd#2694, a new field, `TaskRun.Status.ResourceResults.ResourceName` was added to replace `...ResourceRef.Name` with a more semantically appropriate field. This change finishes the work by removing the deprecated `TaskRun.Status.ResourceResults.ResourceRef`. This has been scheduled for removal since April 2021. Signed-off-by: Andrew Bayer <[email protected]>
c518155
to
7fc46ee
Compare
@lbernick Done, I hope. =) |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
/lgtm
It looks like, even if not used, request-pr-docs-reviewer-wjfgm-clone-repo:
pipelineTaskName: clone-repo
status:
completionTime: "2022-07-04T08:57:17Z"
conditions:
- lastTransitionTime: "2022-07-04T08:57:17Z"
message: All Steps have completed executing
reason: Succeeded
status: "True"
type: Succeeded
podName: request-pr-docs-reviewer-wjfgm-clone-repo-pod
resourcesResult:
- key: url
resourceRef: {}
value: https://github.com/tektoncd/pipeline and $ tkn pr delete request-pr-docs-reviewer-wjfgm -n tekton-ci
Are you sure you want to delete PipelineRun(s) "request-pr-docs-reviewer-wjfgm" (y/n): y
Error: failed to delete PipelineRun "request-pr-docs-reviewer-wjfgm": admission webhook "validation.webhook.pipeline.tekton.dev" denied the request: decoding request failed: cannot decode incoming old object: json: unknown field "resourceRef" I filed #5317 to track the issue |
Changes
See #2694.
The
TaskRun.Status.ResourceResults.ResourceRef
field was only ever used for its ownName
field, and as part of #2694, a new field,TaskRun.Status.ResourceResults.ResourceName
was added to replace...ResourceRef.Name
with a more semantically appropriate field. This change finishes the work by removing the deprecatedTaskRun.Status.ResourceResults.ResourceRef
.This has been scheduled for removal since April 2021.
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
(if there are no user facing changes, use release note "NONE")
Release Notes