[
https://issues.apache.org/jira/browse/NIFIREG-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16469013#comment-16469013
]
ASF GitHub Bot commented on NIFIREG-160:
----------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi-registry/pull/110
Thanks for the quick review. Using the commit message definitely makes
sense, I will add those fields back to the event for creating a flow version.
I think we could support an option to override the commit message as part
of the CLI commands, most likely an optional argument on the
import-flow-version command. Eventually it would be nice to have some kind of
tags (or a better name) that can be put on flows/items, and then the tags could
be used to create these kinds of workflows, but obviously that would be a
longer term effort and using the commit message is a nice option for right now.
I'll keep going on my branch with adding the author and comment fields and
unit tests and then try and get something posted. Thanks for getting the ball
rolling on this, it should be really helpful for users.
> 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)
