[
https://issues.apache.org/jira/browse/NIFIREG-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469486#comment-16469486
]
ASF GitHub Bot commented on NIFIREG-160:
----------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi-registry/pull/117
For an easy way to test this you can turn uncomment the
LoggingEventHookProvider in providers.xml and then use the registry as normal
to create buckets and save flows from NiFi, then tail or inspect
logs/nifi-registry-event.log
> 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)
