[
https://issues.apache.org/jira/browse/NIFI-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17945115#comment-17945115
]
Joe Witt commented on NIFI-14404:
---------------------------------
There was a recent slack thread where it was described that the user could
import such a flow from the registry (a nifi 1.x created flow) into NiFi. But
then the processor was invalid due to the noted property being invalid but also
not visible to delete.
DavidH noted that this may occur now for processors which do not support
dynamic properties or particularly dynamic sensitive properties. The issue
likely has nothing to do with these specific processors but rather is a case we
need to decide how to better handle at the framework level or through user
instructions.
> GetSFTP/PutSFTP processors state is invalid after migrating from
> 1.28.1->2.3.0 using Nifi Registry 1.28.1
> ---------------------------------------------------------------------------------------------------------
>
> Key: NIFI-14404
> URL: https://issues.apache.org/jira/browse/NIFI-14404
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.3.0
> Environment: old: 3 node cluster RH7 nifi version 1.28.1, Registry
> 1.28.1
> new: 3 node cluster RH9 nifi version 2.3.0
> Reporter: Lennart Raun
> Priority: Minor
>
> Hi,
> I'm trying to migrate flows (using Registry client) from old cluster running
> version 1.28.1 to new cluster running 2.3.0 and after downloading a flow from
> Registry containing GetSFTP or PutSFTP, those processors will stay in invalid
> state with error:
> 'Component' is invalid because Sensitive Dynamic Properties [Http Proxy
> Password] configured but not supported
> That property, as expected, is not present in 2.3.0 GUI either to be able to
> remove it.
> Also i have not defined http proxy password or any other proxy related
> parameters on my flow under 1.28.1
> There seems to be several unhandy workarounds: after restarting cluster,
> error disappears, also updating flow in registry, deleting local and
> downloading from registry again does the trick.
> I studied some similar cases like NIFI-10567, but none seems 100% relevant to
> my problem
>
> Thanks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
