[
https://issues.apache.org/jira/browse/NIFIREG-190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16573572#comment-16573572
]
ASF GitHub Bot commented on NIFIREG-190:
----------------------------------------
GitHub user jdye64 opened a pull request:
https://github.com/apache/nifi-registry/pull/133
NIFIREG-190
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jdye64/nifi-registry NIFIREG-190
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/133.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #133
----
commit 6821dc10bd633fec324c2ca82616269dbc8cda0b
Author: Jeremy Dyer <jeremydyer@...>
Date: 2018-08-08T17:41:42Z
NIFIREG-190 Add support for whitelist filtering Event Hook providers
commit 673734cf0a2298a68c6d7921fe8b626a6706567f
Author: Jeremy Dyer <jeremydyer@...>
Date: 2018-08-08T17:43:06Z
Fixed git issue where I had accidentally removed tracking for
NifiRegistryApiApplication.java
commit a527fbaf1ca31a9e03aa4093b9ca639057343cc0
Author: Jeremy Dyer <jeremydyer@...>
Date: 2018-08-08T17:44:11Z
Removed unused imports
----
> Support for Event Whitelisting in the Registry Event Hooks
> ----------------------------------------------------------
>
> Key: NIFIREG-190
> URL: https://issues.apache.org/jira/browse/NIFIREG-190
> Project: NiFi Registry
> Issue Type: New Feature
> Affects Versions: 0.2.0
> Reporter: Jeremy Dyer
> Assignee: Jeremy Dyer
> Priority: Major
> Fix For: 0.3.0
>
>
> Today when an event hook is configured it will be invoked for all of the NiFi
> Registry events. While a user can parse the arguments in the script and
> manually write scripts which ignore certain events it makes more sense to
> provide this event whitelisting the the registry itself.
> I propose adding a new property called something like "Event Whitelist" to
> the current configuration logic. If this property is not present things
> should continue to operate just as they do now, AKA the script is sent all of
> the events, if the property is specified it should contain a comma delimited
> list of events that the hook provider should be triggered for.
> This will be extremely useful when providers that do not provider any sort of
> filtering logic like the script hook provider come along.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
