You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Kevin Doran (JIRA)" <ji...@apache.org> on 2018/08/20 16:58:00 UTC

[jira] [Resolved] (NIFIREG-190) Support for Event Whitelisting in the Registry Event Hooks

     [ https://issues.apache.org/jira/browse/NIFIREG-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Doran resolved NIFIREG-190.
---------------------------------
    Resolution: Done

> 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)