[jira] [Commented] (NIFIREG-160) Implement a hook provider

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFIREG-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468927#comment-16468927 ] 

ASF GitHub Bot commented on NIFIREG-160:
----------------------------------------

Github user bbende commented on the issue:

    https://github.com/apache/nifi-registry/pull/110
  
    @pvillard31 I branched off your commit and resolved conflicts and took a stab at making the the event publishing/consuming asynchronous so that the main request path won't be impacted by any hang-ups from the providers. 
    
    Also tried to make the event concept a little bit less specific to flows so that it can be easily re-used for any other types of items that we may store in the registry like extensions, assets, etc.
    
    My branch is here: https://github.com/bbende/nifi-registry/commits/hook-provider
    
    Let me know what you think about this approach. If we want to head down this path I can submit a PR to your branch, or I can open a new PR against registry that includes your commit + these changes. In the meantime I'll work on some unit tests.


> Implement a hook provider
> -------------------------
>
>                 Key: NIFIREG-160
>                 URL: https://issues.apache.org/jira/browse/NIFIREG-160
>             Project: NiFi Registry
>          Issue Type: New Feature
>            Reporter: Pierre Villard
>            Assignee: Pierre Villard
>            Priority: Major
>
> In order to extend NiFi Registry and NiFi CLI features to integrate with automated deployment pipelines, it would be useful to provide a hook extension point that can be configured by users to trigger actions when a new flow snapshot version is committed in the Registry.
> A first implementation of this extension point could be a "script hook": a script would be executed when a new flow snapshot version is committed. Arguments passed to the script would be: bucket ID, flow ID, version, author and comment.
> This would enable a lot of scenarios including automatically deploy flows from one environment to another.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)