They remain in production. The values of the parameters from registry are only used when creating a new context because one doesn't exist yet, or when adding a new parameter because it doesn't exist in the existing context.
On Mon, Mar 2, 2020 at 2:45 PM Nifi Rocks <[email protected]> wrote: > > Ok, the next time I transport, the overwritten values remain in production or > I have to update them each time? > > Bryan Bende <[email protected]> schrieb am Mo., 2. März 2020, 20:19: >> >> When you save a version of the flow from your test NiFi to NiFi >> Registry, it will include any referenced parameter contexts, along >> with any non-sensitive values. >> >> When you import this flow from NiFi Registry to production NiFi, it >> will look for existing parameter contexts with the same names... >> >> If a matching context is found, it will use it, and add any missing >> parameters. >> >> If a matching context is not found, it will create it. >> >> At this point you can go into the parameter contexts in production and >> update any values to make them specific to your production >> environment, and provide any sensitive values required to make the >> flow run. >> >> On Sat, Feb 29, 2020 at 2:03 PM Nifi Rocks <[email protected]> wrote: >> > >> > Hi community, >> > I have a setup with two nifi instances. One test instance and one >> > production instance. Now I use the Nifi Registry as intermediary. How do I >> > make the contents of the parameter context change depending on the >> > instance? >> > >> > Best >> > Rock
