Re: Suggestions for Flow Development Lifestyle

i know that when we export xml as template, ids are not preserved (what we have on canvas vs on generated temp[ate xml). I wonder about ids from deployment from nifi registry are they preserved ? Best Regards, *Emanuel Oliveira* On Tue, Feb 25, 2020 at 8:57 PM Kevin Doran wrote: > I’ve alway

Re: Suggestions for Flow Development Lifestyle

I’ve always thought along the lines Otto suggests, that eventually, given some way of formatting the diff, there would also be some visual tool in the ecosystem that would help visualize that diff and could be used specifically in the context of reviewing/merging changes. Lots of good discussio

Re: Suggestions for Flow Development Lifestyle

-or- when diffing, some other representation could be presented other than straight xml. The diff ( if run / visualized in nifi ) needn’t be byte for byte, it can be logical can’t it? On February 25, 2020 at 14:58:24, Eric Secules (esecu...@gmail.com) wrote: Hi Ken, > I feel like there are al

Re: Suggestions for Flow Development Lifestyle

Hi Ken, > I feel like there are also issues in trying to build a pull-request-like > workflow, in that most NiFi design is done visually on the canvas but there > isn't a good way, that I know of, to represent differences between versions > in a visual way. Even if you enabled pull request-like f

Re: Suggestions for Flow Development Lifestyle

Eric Yep sounds good - you clearly have a good handle on this and a good vision for where it could be. Please do engage more on this topic with the team as we make improvements going forward. Thanks! On Tue, Feb 25, 2020 at 11:02 AM Eric Secules wrote: > Hi Joe, > > Thanks for confirming my s

Re: Suggestions for Flow Development Lifestyle

Hi Joe, Thanks for confirming my suspicions. I have seen NIFIREG-260 and the associated PR on GitHub , but it’s been almost a year since the last time the PR was published to. I think the best way f

Re: Suggestions for Flow Development Lifestyle

I have a lot of interest in this too, as my team has run into these issues as well. I feel like there are also issues in trying to build a pull-request-like workflow, in that most NiFi design is done visually on the canvas but there isn't a good way, that I know of, to represent differences betwee

Re: Suggestions for Flow Development Lifestyle

-- > *From:* Eric Secules > *Sent:* Tuesday, February 25, 2020 1:31 AM > *To:* users@nifi.apache.org > *Subject:* Suggestions for Flow Development Lifestyle > > Hello everyone, > > Im starting to use nifi and nifi registry on my development team and we're > runni

Re: Suggestions for Flow Development Lifestyle

u describe. From: Eric Secules Sent: Tuesday, February 25, 2020 1:31 AM To: users@nifi.apache.org Subject: Suggestions for Flow Development Lifestyle Hello everyone, Im starting to use nifi and nifi registry on my development team and we're running into issues working together on the same ve

Re: Suggestions for Flow Development Lifestyle

Eric You wrote a great email and all your points make a lot of sense. I'll be blunt and state - we didn't design for that and we should have. When we launched the NiFi Registry we were seeing a lot of large scale monolith NIFi clusters being deployed where each cluster ran the flows of many diff

Suggestions for Flow Development Lifestyle

Hello everyone, Im starting to use nifi and nifi registry on my development team and we're running into issues working together on the same versioned process groups. The nifi registry doesn't support branching, merging and code review nativly so we all have ended up developing on the same branch o