[
https://issues.apache.org/jira/browse/NIFIREG-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468998#comment-16468998
]
ASF GitHub Bot commented on NIFIREG-160:
----------------------------------------
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi-registry/pull/110
@bbende thanks for working on this! I really think it'll be a nice addition
to the NiFi Registry and what you did looks great. I think it's best to close
this PR and you submit a new one. It'll be easier, and I'll be happy to review
it.
I'd just recommend keeping author and comment fields in the Event objects.
Reason is: I'd imagine people that could add a specific tag in the comment to
trigger automatic actions. Example, I have a flow I'm working on in Dev, and I
consider the version I got is ready enough to get tested in Staging and
deployed in production. I could commit my changes and comment with something
like "[STAGING-READY]". This way, the deployment of the workflow in Staging
would be automatically triggered.
I actually think it could be interesting to allow users overriding the
comment when importing a new flow version from one registry to another. This
would ease automatic deployment across multiple environments using the above
mechanism. Just an idea... there could be something better. Do you have
something in mind on your side?
> 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)
