[
https://issues.apache.org/jira/browse/NIFIREG-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602697#comment-16602697
]
Julian Gimbel commented on NIFIREG-139:
---------------------------------------
Hi,
we are versioning and deploying some process groups that reference controller
services (CS) that are defined outside of the process group e.g.
KeytabCredentialsServices for QA and Production. Now if we want to deploy the
process group we still need to manually select the correct CS in the processors
on production like for example in PutHDFS. Would it be possible to include a
“map cs by name” parameter to the CLI so that it walks through the processors
and if it finds a CS with the same name as in the source it will use that one?
I know that currently only the ID is stored, but that one differs between the
two Nifi instances.
Best regards
Julian
> 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)
