Apache NiFi Community,
I am pleased to announce that NIP-1 has passed the vote:
6 +1 (binding) votes
0 +1 (non-binding) votes
0 0 votes
0 -1 votes
Thanks to all who voted! Jiras in the NIFI project will now be created to
cover the implementation.
On Wed, May 7, 2025 at 2:25 PM Matt Burgess <mattyb...@apache.org> wrote:
> All,
>
> I would like to call a vote for NIP-1 [1] to add a
> VerifiableRegistryClient interface to verify Registry Client
> implementations. I can't find the DISCUSS thread in the archive but there
> was a reply from Bryan Bende on Oct 8, 2024, quoted here:
>
> "It seems like a reasonable change to me and would be a nice
> improvement for the user experience when configuring registry clients.
>
> It might be worth noting that although the change to nifi-api is just
> one new interface with one method, there is a significant amount of
> framework level work to make it usable in NiFi. I believe it would
> require....
> - New REST end-points in ControllerResource for submitting and
> checking async verification requests for registry clients
> - The service layer code that performs the handles the async verification
> - UI work on the registry client config screen to call the new REST
> API and show results
> - The implementation of verify for any existing registry clients in
> the codebase that choose to provide it
>
> I don't see any issues with implementing any of the above, but just
> wanted to make sure everyone is on the same page about what is
> involved to fully implement the feature."
>
> If the vote is successful I will create the Epic and associated Jiras in
> the NIFI project for all the work needed.
>
> I'm a +1 (binding) :)
>
> Thank you,
> Matt
>
