nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy LoPresto <>
Subject Re: NiFi Workflow deployment
Date Tue, 15 Aug 2017 19:01:45 GMT
Hi Steven,

This is a common problem which we are actively working to improve. Currently, the “Variable
Registry” [1] feature is a stop-gap solution in conjunction with publishing and loading
templates [2] into the various environments. The new Flow Registry [3] feature will make this
much easier and automate the process for you. You can read about the feature roadmap and if
you search these mailing lists [4][5] for “SDLC” or “flow registry” you can find many
other users discussing their solutions and tips for similar experiences. Hope this helps.

[1] <>
[3] <>
[4] <>

Andy LoPresto
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Aug 15, 2017, at 2:50 PM, Byers, Steven K (Steve) CTR USARMY MEDCOM JMLFDC (US) <>
> Hi.
> Can someone describe the best way to maintain, configure and deploy
> workflows to various NiFi instances?  The project I work on has three DEV
> and three TEST instances.  Our workflows have host-specific values and
> flow-specific values so we want to be able to automate configuring the flows
> and deploying them to the various servers.  NiFi out of the box doesn't seem
> to support doing what we need to do.
> We are, currently, using NiFi 1.1.2.
> Any suggestions would be greatly appreciated!
> Thank you,
> Steven K. Byers

View raw message