Attributes filters in Triggers#1643
Conversation
|
Don't we need to pick the broker changes for the filter to take effect as well? |
Isn't that already here? |
whoa, I guess I totally just missed that, my apologies for the noise :( |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Harwayne, nachocano 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 |
|
The following is the coverage report on pkg/.
|
…ve#1643) * Different cron times for branches * Wrap function invocations in quotes * Add instructions Signed-off-by: Pierangelo Di Pilato <pierdipi@redhat.com> Co-authored-by: Ali Ok <aliok@redhat.com>
Fixes #1610
This work is a subset of @grantr filtering PR. The credit should be his, although if I messed up porting the changes, then is my fault :)
Proposed Changes
attributesfilter to the Trigger spec accepting a map of attribute keys and values to compare to the event context attributes, including extensions. ReplacessourceAndType.sourceAndType, if a value in the attributes map is set to the empty string, then it will match anything.Release Note