Pierre Villard commented on NIFI-4875:

[~spotty] - are you requesting this feature for NiFi Docker image only or also 
the NiFi standard build ?

I see how this could be interesting for the Docker image and that should not be 
really hard to do: passing a variable environment to specify the URL of the 
registry, and if the variable exists, then we initialize the flow.xml.gz with a 
registry client that will reference the variable.

> 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

Reply via email to