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

ASF subversion and git services commented on NIFI-10918:
--------------------------------------------------------

Commit 2473683ce59e187b98af6be1bb7b0f2e046a0986 in nifi's branch 
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2473683ce5 ]

NIFI-10918: When fetching a flow from a Flow Registry, if it references any 
'internal versioned flows' instead of requiring that we have a client 
configured for the appropriate URL, attempt to fetch the flow from each client. 
We will start with the clients that do report that they can handle the URL but 
will try others as well. As soon as we successfully fetch the flow, we stop.

NIFI-10918: Fixed checkstyle violations

This closes #6736
Signed-off-by: Bence Simon <bsi...@apache.org>


> 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: 1h
>  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)

Reply via email to