One way we are currently doing this is: Expose limited set templates (those
will work with pre-defined sources and destinations) to users in a custom
portal, ask user specific configurations in the UI (custom) based on template
selection and integrate this UI with NiFi using REST.
From: Dominique De Vito <ddv36...@gmail.com>
Reply-To: "firstname.lastname@example.org" <email@example.com>
Date: Monday, 12 February 2018 at 11:18 AM
To: "firstname.lastname@example.org" <email@example.com>
Subject: Best Pratices for implementing a source catalog for Nifi
I just wondering what are the Best Pratices for implementing a source catalog
I mean the following:
* Nifi is able to catch data from various sources, and that's just fine (there
are plenty of processors!)
* In a more constrained world, I would like to limit the sources a Nifi
(workflow) developer is able to select (and then, to connect to).
So far I have not seen a way to do so.
The single way I see (currently) is the following one:
* derivate existing processors
* when a (to be modified) processor offers a free-form choice, transform it (if
needed) into a choice into a list of N options (let's say for example N
possible Kafka clusters as sources, and no more than the referenced ones).
Is there another way than derivating the existing processors?