[jira] [Commented] (NIP-1) Add VerifiableRegistryClient interface to verify Registry Client implementations

["Matt Burgess (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIP-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890238#comment-17890238 ] 

Matt Burgess commented on NIP-1:
--------------------------------

Consolidating Bryan's and Matt's comments here, a "full" implementation would include:

- 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, such as EditRegistryClient dialog adding the PropertyVerification component
- The implementation of verify for any existing registry clients in
the codebase that choose to provide it, such as JerseyNiFiRegistryClient

> Add VerifiableRegistryClient interface to verify Registry Client implementations
> --------------------------------------------------------------------------------
>
>                 Key: NIP-1
>                 URL: https://issues.apache.org/jira/browse/NIP-1
>             Project: NiFi Improvement Proposal
>          Issue Type: New Feature
>            Reporter: Matt Burgess
>            Priority: Normal
>              Labels: nifi-registry
>
> Motivation
> To verify basic connectivity from a NiFiRegistryClient to a Registry instance
> Scope
> Add VerifiableRegistryClient interface to verify NiFiRegistryClient implementations
>  
> Compatibility
> Existing implementations in Apache NiFi will need to implement the verify() method, but a default no-op implementation will be offered so as not to interrupt compatibility. The no-op implementation should log/report that no actual verification was applied.
> Description
> Registry Clients didn't exist when the Verifiable (ControllerService, Processor, ReportingTask, ParameterProvider, etc.) interfaces were added.
> Verification
> Implement the verify method for JerseyNiFiRegistryClient (contributed as a separate Jira) and run with a live instance, validating that incorrect configurations return error message(s) and a correct configuration returns success. Fetching the available buckets should suffice for verification, whether buckets exist or not.
> Alternatives
> None identified, current behavior does not allow verification of NiFiRegistryClient instances



--
This message was sent by Atlassian Jira
(v8.20.10#820010)