-
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 taskref/pipelineref deprecated bundle field #7789
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
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 @vdemeester , this looks generally good and thanks for helping with the codebase hygiene - just one question do we want to tombstone the field? Having this on my mind because perviously there were several fields regarding PipelineResources
brought back for tombstone after getting removed. 🤔
docs/pipelines.md
Outdated
taskRef: | ||
name: echo-task | ||
bundle: docker.com/myrepo/mycatalog | ||
taskRef: |
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.
NIT: tabs look a bit off here?
eded993
to
070bf5d
Compare
Ah good point, that might be a problem for results or chains, so we could "keep" it in code, but do nothing. |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
There's some context here: #6430
+1 removing the field can be problematic which is what we saw with PipelineResources. @wlynch explains the intricacies here: #6430 I believe it comes down to, let's prevent resources from being created with this attribute on release X. Then, when release X is the oldest supported release, we can safely drop the attribute. |
070bf5d
to
02a8d6d
Compare
Yes, that definitely make sense. We could start disallowing the field in the next release (or the release that ships this PR) while keeping the field for "clients" like chains… I can update the PR that way indeed. |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
02a8d6d
to
461cb69
Compare
Updated with :
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Looks like we'd also need to get rid of the feature flag (also in the CI maybe 🤔 ) |
3dde7ac
to
05da748
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
da9c62d
to
40c5489
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
40c5489
to
3b00212
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Do we need a lgtm from another company? if not I can lgtm this |
3b00212
to
4a30c25
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
This field has been deprecated for about a year and half. So this is "removing" this field from v1beta1 (it's not present in v1 already). The field is kept in the go code to provide a backward compatibility for client code (like chains, …) but it will be disallowed by the webhook. It will also be completely ignore by the rest of the code. Signed-off-by: Vincent Demeester <[email protected]>
4a30c25
to
0c72d59
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chitrangpatel, JeromeJu 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 |
Changes
This field has been deprecated for about a year and half. So this is
removing this field from v1beta1 (it's not present in v1 already).
Closes #7411
Signed-off-by: Vincent Demeester [email protected]
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes