[jira] [Commented] (NIFI-10918) If NiFi Registry URL changes, flows containing inner versioned flows cannot be fetched

["Simon Bence (Jira)" <ji...@apache.org>]

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

Simon Bence commented on NIFI-10918:
------------------------------------

Test scenario for the PR in order to be merged:

NIFI-10918 TC #1

[Scenario]
Given 2 NiFi Registries (R1 and R2) are started (on the same host but using different port)
And NiFi N1 is started
And R1 and R2 registries are added to N1 as registry clients
When process grop F1 is created and filled with content
And F1 is added to be version controlled under R1
And remove F1 from the canvas
And process grop F2 is created and filled with content
And add F1 as content to F2
And F2 is added to be version controlled under R2
And remove F2 from the canvas

Given stop R1 and R2
And chagne the API port of R2 to R1's API port in the NiFi Registry properties
And change the API port of R1 into a different on (also different from R2's API port) in the NiFi Registry properties
And start R1 and R2
And ports are adjusted in the registry client properties within N1

When process group F2 is added to the canvas from R2
Then N1 should be able to successfully fetch F1 from R1 

[Notes]
By this cumbersome port change, N1 should try to acquire F1 from R2 first (as after the changes it has R1's old URI), but fails and should fall back the now "non matching" R1, successfully fetching the nested flow

> If NiFi Registry URL changes, flows containing inner versioned flows cannot be fetched
> --------------------------------------------------------------------------------------
>
>                 Key: NIFI-10918
>                 URL: https://issues.apache.org/jira/browse/NIFI-10918
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.20.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> I was performing some testing of integration with NiFi Registry. I started with an insecure registry running on [http://localhost:18080|http://localhost:18080/]
> I created a simple dataflow, called 'Inner Flow'. I then versioned it. Afterwards I put its parent Process Group ('Outer Flow') under Version Control.
> Everything worked as expected. I then wanted to verify that things still worked when secured. I secured my registry, changing the URL to [https://localhost:18443|https://localhost:18443/]
> Unfortunately, this resulted in no longer being able to check out the flow 'Outer Flow'. It failed because when the flow was created, it stored the coordinates of 'Inner Flow' as [http://localhost:18080/....] but now it can no longer find any Registry Client that can handle [http://localhost:18080/...] since the client has now been reconfigured to use the HTTPS based URL.



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