[
https://issues.apache.org/jira/browse/NIFIREG-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358918#comment-16358918
]
Kevin Doran commented on NIFIREG-139:
-------------------------------------
{quote}If it is at a higher level then it is an external reference and will not
be copied but rather an attempt to bind to a similar one in the other
environment will be made.{quote}
I'm not sure this is true for controller services. [~markap14] could verify.
> Nifi registry should pick up the controller service definitions while
> deploying a flow
> --------------------------------------------------------------------------------------
>
> Key: NIFIREG-139
> URL: https://issues.apache.org/jira/browse/NIFIREG-139
> Project: NiFi Registry
> Issue Type: Bug
> Affects Versions: 0.1.0
> Reporter: ohad israeli
> Priority: Critical
>
> I am trying to use the registry to copy a simple flow for example of
> httprequest->joltconversion->httpresponse.
> This flow is using the internal http context service which is installed and
> configured on the source (dev env). While deploying the flow to the target
> (prod env) the flow cant find the service on the target (prod end)
> to summarize, on deployment of a flow if the flow is using a service
> controller its setting should also be deployed on the target machine
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
