[NIFI-9075] Problem with 0.5.0 C2 server converting template

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.14.0
• Component/s: MiNiFi
• Environment: 0.5.0 Command and Control server converting template in NiFi 1.12.1 for 1.14.0 MiNiFi
• Assignee: Unassigned
• Reporter: Jeremy
• Created: 23/Aug/21 13:33
• Updated: 23/Aug/21 13:33

Description

If I download my template and use the mini-toolkit-1.14.0 to convert the template there is no issue with the remote process group target port id so the template should be good.  But querying the C2 server config api produces the incorrect yaml file ids, fails the toolkit validation, also given as an error in the MiNiFi log.  From the good vs bad yaml I can see that it picked up the port id rather than the port target id when using the C2 server transformation.
 
Error from MiNiFi:
2021-08-22 23:46:38,452 ERROR [pool-3-thread-1] o.apache.nifi.minifi.bootstrap.RunMiNiFi Unable to carry out reloading of configuration on receipt of notification event
java.io.IOException: Unable to successfully transform the provided configuration
Caused by: org.apache.nifi.minifi.bootstrap.exception.InvalidConfigurationException: Failed to transform config file due to:[Connection with id caaf52c3-c29f-34d4-0000-000000000000 has invalid destination id 5c035c8f-c4d4-3d9b-5a40-210870fced8c]
 
NiFi input port XML:
 
                <inputPorts>
                    <batchSettings/>
                    <comments></comments>
                    <concurrentlySchedulableTaskCount>1</concurrentlySchedulableTaskCount>
                    <connected>true</connected>
                    <exists>true</exists>
                    <groupId>4cbe2f91-6d36-3327-3f49-6d7cc6b08340</groupId>
                    <id>5c035c8f-c4d4-3d9b-5a40-210870fced8c</id>
                    <name>MiNiFi Raw Data</name>
                    <targetId>2f5a4d17-0175-1000-0000-000050346b1e</targetId>
                    <targetRunning>true</targetRunning>
                    <transmitting>false</transmitting>
                    <useCompression>false</useCompression>
                </inputPorts>
 
Bad yaml:

• id: caaf52c3-c29f-34d4-0000-000000000000
    name: Set Version Headers/success/5c035c8f-c4d4-3d9b-5a40-210870fced8c
    source id: 9b2797ba-c156-3c13-0000-000000000000
    source relationship names:
    - success
    destination id: 5c035c8f-c4d4-3d9b-5a40-210870fced8c
   
  Good yaml:
• id: caaf52c3-c29f-34d4-0000-000000000000
    name: Set Version Headers/success/2f5a4d17-0175-1000-0000-000050346b1e
    source id: 9b2797ba-c156-3c13-0000-000000000000
    source relationship names:
    - success
    destination id: 2f5a4d17-0175-1000-0000-000050346b1e