Hi, I also like the idea! Currently we're solving it by periodically running ansible scripts on the machines. That script connects to our enterprise intranet Artifactory/Nexus and pulling the custom nars as maven does (groupid, artifactid, version, nar) Maybe, directly pulling from a mvn-repository could solve the versioning problem. Of course, we would have to keep the list of nars somewhere.
Kind regards, Felix Am 7. Januar 2025 11:22:38 MEZ schrieb nathan.engl...@bt.com.INVALID: >Hi Pierre, > >I very much like the idea of this and can immediately see the benefits >especially when it comes to distributing custom NARs. > >It's been a few years since I've had to use NiFi for anything more than a >quick tactical tool for data migration. So, forgive me if this functionality >already exists! > >Would the plan be to pull these from an external CDN directly to NiFi node in >the cluster, or via single point acting as a proxy e.g. NiFi Registry? I see >pulling from the internet is good, but I feel a local(to the environment) copy >would be needed to quickly add new nodes during scaling, or in the event the >remote copy is no longer available. > >A way to completely disconnect from the internet in quite a few of our >scenarios would be required, but we can mirror CDNs (within reason). > >In terms of distributing custom NARs, as I mentioned above a solution where we >can host our own repository of NARs would be great too. > >How would version control be handled? E.g. there is a new version of an NAR, >would you need to manually update the processor, or would it be automatically >updated for the flow? I see benefits of both. > >Kind Regards, > >Nathan > >-----Original Message----- >From: Pierre Villard <pierre.villard...@gmail.com> >Sent: 04 January 2025 18:05 >To: dev@nifi.apache.org >Subject: [DISCUSS] Extension Registry Clients > >Hi NiFi community, > >As we're trying to flush out all of the details of the new NIP process [1] >when it comes to proposing significant changes to NiFi, I'd like to start this >discussion thread regarding a NIP that I submitted about Extension Registry >Clients [2]. > >I invite every interested individual to have a look at the proposal, and share >feedback via the comments of the JIRA or via this thread. A formal vote can >then be done to accept or reject the proposal. > >TL;DR this NIP is about adding a new component type in NiFi: the extension >registry clients. The concept of NAR Manager has already been added in NiFi >2.0 and it's possible to PUSH NAR files into NiFi via new APIs. The goal here >is to provide a PULL mechanism to fetch NARs from external locations. > >Thanks a lot! >Pierre > >[1] >https://cwiki.apache.org/confluence/display/NIFI/NiFi+Improvement+Proposal+Process >[2] https://issues.apache.org/jira/browse/NIP-4
