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

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

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi-registry/pull/117

    NIFIREG-160 Implement a hook provider

    For whoever reviews/merges this, please keep the commit history and don't 
squash.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi-registry hook-provider

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi-registry/pull/117.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 #117
    
----
commit 3371a07068dbbd5b3984f386cf61bc297ba608a9
Author: Pierre Villard <pierre.villard.fr@...>
Date:   2018-04-06T14:58:33Z

    NIFIREG-160 - Initial hook provider

commit f99cf19d49bf5d301ada83a5c128b645da00458f
Author: Bryan Bende <bbende@...>
Date:   2018-05-08T17:38:33Z

    NIFIREG-160 - Making event hooks asynchronous

----


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

Reply via email to