[
https://issues.apache.org/jira/browse/NIFI-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362150#comment-16362150
]
Daniel Oakley commented on NIFI-4875:
-------------------------------------
Hi [~pvillard] , I think it would be good in the standard build. I am using a
custom docker image anyway.
I would still hope after initializing the flow.xml.gz the Nifi controller is
aware the flow was sourced from the nifi-registry, so that updates can be
detected and applied as per normal operation when nifi is integrated with the
registry.
Another issue that this relates to, which I am not sure is nifi or registry
related, is that nifi seems only to store a process group in the registry, not
an entire flow. So it is not clear to me how a new Nifi could be initialized
with a flow stored in the registry without first creating a new flow, and then
adding a process group that loads a stored registry flow into it. Or can a
process group saved to the registry be extracted as a new top-level flow that
doesn't require the manual addition of a process group? I find that requirement
somewhat strange and confusing.
> Import flow from nifi-registry on bootstrap/initial start
> ---------------------------------------------------------
>
> Key: NIFI-4875
> URL: https://issues.apache.org/jira/browse/NIFI-4875
> Project: Apache NiFi
> Issue Type: Wish
> Components: Flow Versioning
> Affects Versions: 1.5.0
> Reporter: Daniel Oakley
> Priority: Major
> Labels: registry
>
> As I user I would like to be able to automate the deployment of a new Nifi
> instance (e.g. using Docker, Ansible), and have that instance load a specific
> versioned flow from the nifi-registry and start running it automatically.
> To enable this I would like to be able to specify the nifi-registry URL in
> nifi properties file, and the flow to load/start via either the properties
> file or a command line option.
> This will greatly increase the ease of deploying nifi in automated
> environments such as Kubernetes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
