nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Taft <>
Subject Re: promoting flow configuration file from one environment to the other
Date Tue, 14 Jul 2015 16:13:37 GMT

Most processor support the use of Expression Language for these types of
properties.  For example, InvokeHTTP uses the Expression Language for the
URL property.

Further, the NiFi EL can be configured to pull values from environment
variables or Java system properties.  Either of these options should allow
you to run the same flow.xml.gz in multiple environments, with the
appropriate values passed in from the NiFi host environment on startup.

I believe there is more documentation on this capability in the Expression
Language Guide. [1]

Give it a try and shout out if you have any questions.  Good luck.



On Tue, Jul 14, 2015 at 10:49 AM, Beharry, Allan D <> wrote:

> Classification: UNCLASSIFIED
> Hello,
> I am running Nifi on one environment and would like to be able to take
> that flow.xml.gz and put it in a different environment (e.g. from staging
> to production).  Problem is that currently we have processors that have
> configurations that are environment specific.  As an example, we could use
> the InvokeHTTP processor and the remote URL property is specific to the
> environment.  This means that if I take the flow.xml.gz from one
> environment to the other, I have to manually go in and change the remote
> URL property.  This is less than ideal.
> I would like to minimize the amount of manual work required in moving a
> flow configuration from one environment to the next.
> How would I achieve this?
> Thanks,
> Allan

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message