Parameter contexts were added after the use of templates was no longer recommended and substantially deprecated and NiFi Registry was selected as the managed flow definition version control and environment promotion system. There are future efforts to facilitate the export/import of flow segments directly to/from a NiFi instance without NiFi Registry but they are not released yet.
Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com He/Him PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jul 28, 2020, at 2:00 PM, bsavard <bob.sav...@aifoundry.com> wrote: > > Hi, > > I have a flow that uses parameter contexts. I understand that the parameter > context definitions themselves are persisted to flow.xml.gz. > > However, when I save my flow as a template, delete the flow from the canvas, > then add the template back onto a blank canvas, all of the processor context > assignments I made are gone. When I download and search the template file > itself, there's no reference to the parameter context assignments. > > So, where are the assignments stored? And how would I go about deploying > this template to many servers without someone having to manually go back > into the flow on each server and adding the assignments all over the place? > We don't use NiFi Registry; we use a traditional Maven based deployment > cycle. > > TIA! > > > > -- > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
