-
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
[TEP-0137] Rename customrun package #6884
Conversation
82e4a78
to
8e274a7
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
8e274a7
to
75b175b
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
The pkg/reconciler/customrun package contains a controller that today sends cloudevents for CustomRuns. In the context of TEP-0137, more controllers will be added to send events for all resources, so the current name does not make sense anymore. Renaming the package to "notifications/customrun", so that the notifications package may hold the various controllers for the different kind of resources. The "events" and "cloudevents" names are already used elsewhere and we don't want a mass API rename for this. We might consolidate the code further as a follow-up. The new name is also more future-proof, as the controllers may in future handle other kinds of non-cloudevents type of notifications. When renaming I realised that the customrun controller was being started as part of the main controller as well as an independent one. This PR fixes that bug as well. Signed-off-by: Andrea Frittoli <andrea.frittoli@uk.ibm.com>
75b175b
to
ea090ba
Compare
The following is the coverage report on the affected files.
|
/retest |
/test pull-tekton-pipeline-go-coverage-df |
@afrittoli: The specified target(s) for
The following commands are available to trigger optional jobs:
Use 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. |
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-beta-integration-tests |
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
One question though - would this break downstream customrun implementations? Should we leave behind a simple package that type aliases to the new package?
If this is truly only for cloudevent notifications, you may also want to add a doc.go
with some documentation calling this out.
/approve cancel (approve was set before LGTM - undo-ing to give a chance to respond to the comment) |
/remove-approve |
Thanks @wlynch - it looks like the un-approve didn't work, so I'll address your comments as a follow-up. If you prefer I can introduce an alias; in #6889 however I started restructuring that package in preparation for "TEP-0137", so I'm not sure an alias would be very helpful (or alternatively I will have rework that PR and the following one to keep the old methods around). |
Dependencies:
Once dependencies are merged, the PR will contain 1 commit only
Changes
The pkg/reconciler/customrun package contains a controller that
today sends cloudevents for CustomRuns. In the context of TEP-0137,
this controller will be repurposed to send events for all resources,
so the current name does not make sense anymore.
Renaming the package to "notifications", because the "events" and
"cloudevents" names are already used elsewhere and we don't want
a mass API rename for this. We might consolidate the code further
as a follow-up. The new name is also more future-proof, as the
controller may in future handle other kinds of non-cloudevents
type of notifications.
When renaming I realised that the customrun controller was being
started as part of the main controller as well as an independent
one. This PR fixes that bug as well.
Signed-off-by: Andrea Frittoli andrea.frittoli@uk.ibm.com
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
/kind misc