Hello, A lot depends on whether you are doing the promotion with the UI or with scripts using something like NiFi CLI or NiPyApi.
1) Currently references to controller services outside the versioned process group need to be set after initial import. In the next release it will auto-select by name as long as there is only one service with the given name and type in a parent group (name is not unique). 2) The snapshot of the variables are part of the versioned flow, so after importing you would have to set the new values in the target environment. This can be done in the UI or with scripts. 3) The REST API allows for positioning of any component that is created. i can't speak for how to do it with NiPyApi, but I know the CLI pg-import command attempts to automatically organize the imported process groups on the root canvas so that they don't overlap. Thanks, Bryan On Thu, Aug 8, 2019 at 4:32 PM sivasankar Reddy <[email protected]> wrote: > > Hi, > > We are looking for nifi deploy automation from regsitry -> higher nifi > instance. Quick observations during intial evaluation. > > 1. After process group import, controller services are not set in nifi > instance > 2. How to set variables from source process group to destination process > group. > 3. Is there any possibility of definining the positioning of process group to > be imported in Nifi Canvas. > > Any other best practices regarding NiFi deployment automation will be > helpful. > > Thanks in Advance! >
