[ https://issues.apache.org/jira/browse/NIFI-12394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael W Moser updated NIFI-12394: ----------------------------------- Summary: when importing versioned flow with component that migrates properties, controller service reference is invalid (was: when importing versioned flow with InvokeHTTP, SSLContextService property is invalid) > when importing versioned flow with component that migrates properties, > controller service reference is invalid > -------------------------------------------------------------------------------------------------------------- > > Key: NIFI-12394 > URL: https://issues.apache.org/jira/browse/NIFI-12394 > Project: Apache NiFi > Issue Type: Bug > Components: Flow Versioning > Reporter: Michael W Moser > Priority: Major > > I built a Process Group containing one StandardRestrictedSSLContextService > that is referenced by an 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, 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 old StandardRestrictedSSLContextService > UUID d7d70b6c-abe4-3564-a219-b289cb7f25d2 which does not exist. -- This message was sent by Atlassian Jira (v8.20.10#820010)