Enqueue Triggers on Broker changes without Tracker#3966
Conversation
Signed-off-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
|
The following is the coverage report on the affected files.
|
|
/cc @vaikas |
|
Worked, retesting |
1 similar comment
|
Worked, retesting |
|
/test pull-knative-eventing-conformance-tests |
|
We got 10/10 successful runs in |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matzew, pierDipi The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Signed-off-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
Signed-off-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
Signed-off-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com> Co-authored-by: Pierangelo Di Pilato <pierangelodipilato@gmail.com>
| @@ -66,6 +71,28 @@ func NewController( | |||
|
|
|||
| triggerInformer.Informer().AddEventHandler(controller.HandleAll(impl.Enqueue)) | |||
There was a problem hiding this comment.
we should also filter the trigger changes based on which broker it points to.
There was a problem hiding this comment.
@n3wscott can you explain more what you mean? doesn't the label selector filter by the broker it points to? Or am I misunderstanding.
There was a problem hiding this comment.
This broker impl only needs triggers for brokers. We filter broker changes for triggers but we should do the other side too?
Addresses knative/eventing-contrib#1424 and subtests.
Proposed Changes
Release Note