[
https://issues.apache.org/jira/browse/NIFIREG-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476145#comment-16476145
]
ASF GitHub Bot commented on NIFIREG-160:
----------------------------------------
Github user pvillard31 commented on a diff in the pull request:
https://github.com/apache/nifi-registry/pull/117#discussion_r188350335
--- Diff:
nifi-registry-framework/src/main/java/org/apache/nifi/registry/provider/flow/StandardFlowSnapshotContext.java
---
@@ -33,8 +33,8 @@
private final String flowName;
private final int version;
private final String comments;
- private final long snapshotTimestamp;
--- End diff --
Really nitpick but I think the changes on this class seem unnecessary, no?
> 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)
