[
https://issues.apache.org/jira/browse/NIFI-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383684#comment-16383684
]
Joseph Witt commented on NIFI-4921:
-----------------------------------
+1 to bende's suggested model.
The gist is we want to allow the parameters that can be heavily
instance/deployment environment specific to be decoupled from the flow
configuration itself. The approach he suggests would allow that.
> better support for promoting NiFi processor parameters between dev and prod
> environments
> ----------------------------------------------------------------------------------------
>
> Key: NIFI-4921
> URL: https://issues.apache.org/jira/browse/NIFI-4921
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Flow Versioning, SDLC
> Affects Versions: 1.5.0
> Reporter: Boris Tyukin
> Priority: Minor
>
> Need a better way to promote processor parameters, like "Concurrent tasks"
> from development to production environments.
> Bryan Bende suggested:
> I think we may want to consider making the concurrent tasks work
> similar to variables, in that we capture the concurrent tasks that the
> flow was developed with and would use it initially, but then if you
> have modified this value in the target environment it would not
> trigger a local change and would be retained across upgrades so that
> you don't have to reset it.
>
> I would extend this Jira to similar parameters, that need to be changed
> manually now when promoting flows to production from dev/test environments
> and they cannot use expression language or variables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
