[
https://issues.apache.org/jira/browse/NIFI-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603671#comment-17603671
]
Simon Bence commented on NIFI-10497:
------------------------------------
Thanks for your interest!
You are correct, the integration would remain but with a more loosely coupled
manner. What this means that while the current functionality should work as
before, it would open the possibility to handle versioning using a different
service, like GitHub you mention. Just to be clean: this step would just open
this possibility but it will not contain an actual GitHub integration at this
point.
Your observations with the REST API look accurate in both parts. The existing
endpoints will be "extended" but the current API will not be touched thus in
the controller side (Resources) we will be able to handle both requests both
with the current and the upcoming format. At least one new endpoint is needed
to serve the implementation types known by the NiFi, similar to the identical
endpoints for Processors, Controller Services, etc.
> 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)
