[
https://issues.apache.org/jira/browse/NIFIREG-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605506#comment-16605506
]
Julian Gimbel commented on NIFIREG-139:
---------------------------------------
Two other possibilities come into my mind:
# is to add a new property to the CS that names something like "Mapping Name".
That one can be used to check for equality within the different environments.
That would mean changes in Nifi as well as in Nifi Registry.
If that property is evaluated with the expression language it might give quite
powerful deployment possibilities and much more flexibility.
# As some of the CS already allow for Dynamic Attributes it would also be
possible to use a specifically named dynamic attribute. The name of that
specific attribute can be provided to the CLI as an optional parameter that
would be used to check for name equality. The disadvantage is, that Dynamic
Attributes do not allow
> 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)
