Hi Bryan, Thanks for the update. Does the existing pg-import takes optional params for x/y coordinates. If yes can you share the sample command as pg-import --help doesn't has this info.
Regards, siva On 2019/08/20 22:19:23, Bryan Bende <bbe...@gmail.com> wrote: > Hello, > > 1) pg-import will keeping finding a location that does not overlap with any > existing process groups, so it is more of auto layout. We could easily add > optional params for x/y coordinates. > > 2) Both are fine choices.. CLI is more geared towards simple commands, > where as with NiPyApi you could more easily write complex logic in Python. > With CLI you would write a wrapper shell script that made individual calls > to the CLI. I think it is really just a matter of preference. > > -Bryan > > > On Tue, Aug 20, 2019 at 5:11 PM sivasankar Reddy <mail2ms...@gmail.com> > wrote: > > > Hi Bryan, > > > > Thanks for your input. I would like to know more > > > > 1. how does CLI pg-import works if already canvas has 100 to 150 flows. > > Will CLI pg-import always place the flow in canvas which can be easily > > located. As nipyapi has location(x,y) during deploy flow. > > > > 2. From enterprise usage, do you recommend toolkit CLI vs nipyapi, it > > seems toolkit CLI is part of official Nifi. > > > > Any other points regarding this will be helpful. > > > > Regards, > > Siva > > > > On 2019/08/08 22:41:43, Bryan Bende <bbe...@gmail.com> wrote: > > > 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 <mail2ms...@gmail.com> > > 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! > > > > > > > > > > -- > Sent from Gmail Mobile >
