I'm a big +1 to this proposal. It would solve a huge burden that is keeping NARs up to date in environments where there's alot of teams that share NARs but have separate NiFi deployments and repositories.
On Feb 8, 2017 7:09 PM, "Peter Wicks (pwicks)" <pwi...@micron.com> wrote: > I think a lot of us are facing the same challenges, and this sounds like a > step in the right direction. > I had actually started to dig into a Flow Configuration plugin that would > use Git branches to copy/sync flows between instances/environments, and > keep them versioned; hadn't gotten very far. > > -----Original Message----- > From: Jeremy Dyer [mailto:jdy...@gmail.com] > Sent: Wednesday, February 08, 2017 3:54 PM > To: dev@nifi.apache.org > Subject: Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi > Registry > > Bryan - I think this is a fantastic idea. I would also think this would be > a good place to add a "device registry" as well. It makes much more sense > in my mind to have these efforts in sub projects outside of the nifi/minifi > core. > > On Wed, Feb 8, 2017 at 4:50 PM, Bryan Bende <bbe...@gmail.com> wrote: > > > NiFi Community, > > > > I'd like to initiate a discussion around creating a sub-project of > > NiFi to encompass the registry capabilities outlined in several of the > > feature proposals on the Wiki [1]. A possible name for this > > sub-project is simply "NiFi Registry". > > > > Currently there are two feature proposals that call for NiFi to > > interact with an external registry: > > > > Configuration Management of Flows [2] - This feature proposal calls > > for a flow registry where versioned flows can be published and > > consumed, allowing flows to be easily migrated between environments . > > > > Extension Registry [3] - This feature proposal calls for a place to > > publish NARs containing extensions, allowing NiFi to decouple itself > > from including all of the NARs in the main distribution, and allowing > > better discovery of available extensions. > > > > The idea would be to create a NiFi Registry sub-project, with > > sub-modules for the various registries. These registries could then be > > packaged and distributed as a single artifact and run as a > > complimentary application to NiFi and MiNiFi. NiFi would not require > > the registry application, however, a given NiFi could be configured to > > know about one or more flow registries, or one or more extension > > registries. > > > > Creating a sub-project would allow the registry code to evolve > > independently of NiFi and be released on it's own timeline. In > > addition, it would make tracking issues/work much clearer through a > > separate JIRA. > > > > Please discuss and provide and thoughts or feedback. > > > > Thanks, > > > > Bryan > > > > [1] https://cwiki.apache.org/confluence/display/NIFI/NiFi+ > > Feature+Proposals > > [2] https://cwiki.apache.org/confluence/display/NIFI/ > > Configuration+Management+of+Flows > > [3] https://cwiki.apache.org/confluence/display/NIFI/ > > Extension+Repositories+%28aka+Extension+Registry%29+for+ > > Dynamically-loaded+Extensions > > >
