[
https://issues.apache.org/jira/browse/NIFIREG-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489203#comment-16489203
]
ASF GitHub Bot commented on NIFIREG-160:
----------------------------------------
GitHub user bbende opened a pull request:
https://github.com/apache/nifi-registry/pull/118
NIFIREG-160 Fixing issue where version created event throws an except…
…ion when comments are not provided
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/bbende/nifi-registry NIFIREG-160-exception
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi-registry/pull/118.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 #118
----
commit a1f16a2ac068dcbe9d138b81de10df336d0745fa
Author: Bryan Bende <bbende@...>
Date: 2018-05-24T15:23:16Z
NIFIREG-160 Fixing issue where version created event throws an exception
when comments are not provided
----
> 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: Bryan Bende
> Priority: Major
> Fix For: 0.2.0
>
>
> 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)
