[NIFI-12394] when importing versioned flow with component that migrates properties, controller service reference is invalid

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0.0-M2
• Component/s: Flow Versioning
• Assignee: Michael W Moser
• Reporter: Michael W Moser
• Created: 20/Nov/23 20:59
• Updated: 17/Jan/24 17:21
• Resolved: 17/Jan/24 17:21

Description

I built a Process Group containing one StandardRestrictedSSLContextService that is referenced by one InvokeHTTP processor.  I downloaded that Process Group as a flow definition with external services.  I also versioned that Process Group in NiFi Registry.

Inside the flow definition file, I see the StandardRestrictedSSLContextService with "identifier":"d7d70b6c-abe4-3564-a219-b289cb7f25d2" and InvokeHTTP references that UUID.

When I create a new Process Group using either the downloaded flow definition or the NiFi Registry flow, a new StandardRestrictedSSLContextService is created and it has a new UUID as expected.  The InvokeHTTP processor is invalid because it references the proposed StandardRestrictedSSLContextService UUID d7d70b6c-abe4-3564-a219-b289cb7f25d2 which does not exist.

The service and processor are created and references are updated, but when migrating processor properties and any change occurs, the service reference is reverted back to what was in proposedProperties.

Issue Links

• links to: GitHub Pull Request #8184