Matt, 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. Thanks, Bryan On Tue, Oct 8, 2024 at 7:42 PM Matt Burgess <mattyb...@gmail.com> wrote: > > Team, > > I recently submitted a NiFi Improvement Proposal (NIP) [1] to add a > VerifiableRegistryClient interface to verify Registry Client > implementations. AFAIK Registry clients didn't exist when the rest of the > Verifiable component interfaces were added, but I think it would be a good > idea to verify Registry connections before trying things like starting > version control. > > I invite some discussion about [1] and would like to initiate a vote > starting Oct. 11 since it is new and fairly straightforward, if there are > no objections / concerns. For larger-scope NIPs in the future it may be > necessary to allow more discussion (say, a week?) before voting, but I'm > happy to discuss that as well. > > Eager to hear thoughts about [1] and the NIP process! > > Thank you, > Matt > > [1] https://issues.apache.org/jira/browse/NIP-1
