[jira] [Created] (NIFI-13833) Importing flow json with migrated sensitive properties does not work

["Peter Turcsanyi (Jira)" <ji...@apache.org>]

Peter Turcsanyi created NIFI-13833:
--------------------------------------

             Summary: Importing flow json with migrated sensitive properties does not work
                 Key: NIFI-13833
                 URL: https://issues.apache.org/jira/browse/NIFI-13833
             Project: Apache NiFi
          Issue Type: Bug
            Reporter: Peter Turcsanyi


[Processor.migrateProperties()|https://github.com/apache/nifi-api/blob/d7f7713a70562ca37b22e84110344c3d4e496e0c/src/main/java/org/apache/nifi/processor/Processor.java#L105-L121] can be used for following property configuration changes between NiFi versions automatically. It supports flow.json.gz migration and also migration of exported flow json-s.

When the exported flow contains a component with a sensitive property that should be migrated (e.g. renamed or converted to a controller service plus removed), then the component ends up in invalid state saying: {_}"Component is invalid because Sensitive Dynamic Properties [property_name1, ...] configured but not supported"{_}. Even worse, the old properties are not shown on the UI and cannot be removed manually so the user cannot resolve the invalid state (only via deleting + recreating the component).

Migration of sensitive properties in flow.json.gz works properly. The issue affects the flow export/import scenario only. The root cause seems to be that the exported flow does not contain the sensitive property values so these properties "do not exist" for the migration framework.

Steps to replicate:
 * configure PutS3Object with processor level Access Key ID and Secret Access Key properties using NiFi 1.x
 * export the flow on NiFi 1.x
 * import the flow on NiFi 2.x
 * PutS3Object will be in invalid state on NiFi 2.x



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