-
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 PipelineStatus and PipelineResourceStatus #1640
Conversation
Hi @poy. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
|
/test pull-tekton-pipeline-integration-tests |
/hold |
@poy can you squash your commits ? 👼 |
I updated the release notes in the PR desciription |
@poy also needs a rebase 🙇♂️ |
This removes two struct types: * `PipelineStatus` * `PipelineResourceStatus` These Status types were unused and did not follow the pattern of using Knative's DuckType. Other types such as `Task` do not have a Status type and instead defer to their corresponding `TaskRun` status. fixes tektoncd#1636
@vdemeester Rebased and squashed! |
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.
/hold cancel
/lgtm
/meow
Thanks @poy 🤗
In response to this:
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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
@vdemeester sounds like you're already on this but i think this has some implications for CLI + Dashboard + and also Triggers (@dibyom ) - I just tried to use latest triggers with latest pipelines and got:
|
@bobcatfish ah interesting… because there was no |
They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of tektoncd#1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
See #1762 for backward compat. |
They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of tektoncd#1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of tektoncd#1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of #1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of tektoncd#1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of tektoncd#1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
They are not used, and shouldn't be there, but client that have previous version of this struct would fail targeting the API. This is a *partial* revert of #1640, as it doesn't reintroduce the `UpdateStatus` generation. Signed-off-by: Vincent Demeester <[email protected]>
Changes
This removes two struct types:
PipelineStatus
PipelineResourceStatus
These Status types were unused and did not follow the pattern of using
Knative's DuckType. Other types such as
Task
do not have a Status typeand instead defer to their corresponding
TaskRun
status.fixes #1636
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes