Pierre Villard commented on NIFI-4875:

What you describe is per-design: it's best to isolate independant workflows in 
separated process groups and it's not possible to save the root process group 
in the registry (don't have in mind the specifics around this decision but, in 
a multi tenant environment, you probably would not expect to version everything 
when multiple teams are working on multiple workflows).

Regarding your initial ask, using the REST API or the CLI under development 
(NIFI-4839), it should be easy to import a given version of a given workflow in 
a given bucket. It could be called when launching the Docker image.

> 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