You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (JIRA)" <ji...@apache.org> on 2018/05/15 17:20:00 UTC
[jira] [Resolved] (NIFIREG-160) Implement a hook provider
[ https://issues.apache.org/jira/browse/NIFIREG-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre Villard resolved NIFIREG-160.
------------------------------------
Resolution: Fixed
Assignee: Bryan Bende (was: Pierre Villard)
Fix Version/s: 0.2.0
> 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)