[
https://issues.apache.org/jira/browse/NIFI-10497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609574#comment-17609574
]
ASF subversion and git services commented on NIFI-10497:
--------------------------------------------------------
Commit 94fdc794b09317ebbcb1edf89dd29d286b1b4554 in nifi's branch
refs/heads/main from simonbence
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=94fdc794b0 ]
NIFI-10497 Making RegistryClient an extension point (#6433)
- NIFI-10497 Mae FlowRegistryClient an extension point
> 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
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> 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)
