-
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
[TEP074] Remove CloudEvent pipelineResources #5995
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
68caa7a
to
d6d422f
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
d6d422f
to
4963c84
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
4963c84
to
b53ea48
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
b53ea48
to
1839a7f
Compare
838a0a8
to
fbf9908
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
fbf9908
to
24ea582
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
This commit removes the CloudEvent Resources support. This PR removes , its respective example test, relevant functions in cloud_event_controller and docs for cloud-event resources. Removal of , as in tektoncd#5967 has been broken up into removal of each resources packages for the code standard.
24ea582
to
71e9742
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.
Thank you @JeromeJu, this looks great.
The 'cloudevent_count' metric counts cloudevent sent via the PipelineResource
, so it doesn't make any more sense. I don't think we added metrics to the API stability policy, so it should be safe to remove. Besides, it wouldn't report anything at all.
I noticed that taskRun.status.CloudEvents
has only just been marked as deprecated and is not planned for removal until Oct 2023.
I though that when we deprecated PipelineResources
we also deprecated all parts of the API associated with them, which would include resource inputs/outputs, resource results and cloudevents status. It may be that we were not explicit about the parts of the API affected, but I'm not sure we should keep around an API which is not used by anything.
@tektoncd/core-maintainers thoughts about this?
I don't think this discussion should block this PR, so it's fine to move ahead and possibly further cleanup in a follow-up PR. Perhaps here we could remove the metric at least?
Many thanks @afrittoli for the detailed look into this removal and the respective effects on the related APIs. I have done the following so this PR might get in more safely for now. :)
|
That was my thought as well. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lbernick, 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 |
/lgtm |
Changes
This commit removes the CloudEvent Resources support.
Removal of
pipelineResources
, as in #5967 has been broken up into removal of eachresources packages for the
small PR
code standard.This PR removes
github.com/tektoncd/pipeline/pkg/apis/resource/v1alpha1/cloudevent
the respective example test and docs for cloud-event resources.
Part of #5967
/kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes