[jira] [Commented] (NIFI-10497) Making RegistryClient an extension point

["Mark Payne (Jira)" <ji...@apache.org>]

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

Mark Payne commented on NIFI-10497:
-----------------------------------

[~simonbence] so to be clear - this would allow us to continue to integrate NiFi with a NiFi Registry, the way that it always has worked. But it means we could, in the future, build an integration such that we could treat the file system as a registry, for example? And we could also build an integration directly with GitHub instead of using the NiFi Registry as an intermediate service?

If so, I think this is a great idea! Users have definitely asked for the ability to integrate directly with github, etc. but we haven't had the ability to do so yet. This would be a great first step, to make the extension point a first class citizen.

We will need to ensure, though, that we keep backward compatibility in mind. Any registry client that's already been created should still work. And, as you mention, the REST API should still work. Though I suspect this will require building out additional REST endpoints.

> Making RegistryClient an extension point
> ----------------------------------------
>
>                 Key: NIFI-10497
>                 URL: https://issues.apache.org/jira/browse/NIFI-10497
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Simon Bence
>            Assignee: Simon Bence
>            Priority: Critical
>
> Currently NiFi is capable to connect only to the NiFi Registry as a "registry repository". It would be beneficial to give NiFi the capability to depend on other services.
> In order to this, I suggest to decouple the registry behaviour from the NiFi Registry as much as it is possible (inlcuding but not only the API and the Resources) and move the actual implementation behind this new API.
> To be able to add new implementations, this new API must be an extension point applying the usual NiFi instruments for this. Also it is paramunt to keep the continuity with the current usages and make the implementation capable to process the current REST call format. 



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