[
https://issues.apache.org/jira/browse/NIFIREG-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352620#comment-16352620
]
Joseph Witt commented on NIFIREG-139:
-------------------------------------
[~israelio] If the controller service is scoped/configured within the item
being version controlled it will be included/copied. 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.
If you create the service in the other environment just as you did in the
original environment it will likely do what you want. If you change to have
the CS in the same scope as the versioned item it will too.
Please confirm how you have it setup and let us know if that new understanding
helps you.
Others can confirm if I've stated anything inaccurate here.
> 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)
