I'll see if I can do that, but here's the workflow I went through. We're on 1.21.0 at least for NiFi. Still verifying what version of the registry we're on, but I think it's recent.
1. Create a PG, provide a parameter context on cluster a. 2. Create a base parameter context, assign that to the context from #1 as its parent. 3. Deploy the PG via Registry import on a cluster b 4. Add multiple keys (sensitive or not) to the base context on cluster a 5. Reference keys from #4 in a component in the flow. 6. Save changes on the PG on cluster a 7. Attempt to upgrade the version on cluster b Note: I brought the flow directly into a third cluster and it imported correctly on the first pass. On Thu, Nov 2, 2023 at 10:06 AM Bryan Bende <[email protected]> wrote: > Mike, > > Can you come up with a small reproducible example to create the problem? > > Also, is it the latest version of NiFi Registry? > > > > On Wed, Nov 1, 2023 at 3:14 PM Mike Thomsen <[email protected]> > wrote: > >> I refactored a bunch of related flows to use a base parameter context. I >> added a few changes on my development cluster to a flow including two new >> properties added to the base parameter context. Saved those changes into >> our NiFi Registry, and then upgraded the test cluster to use that new >> version of the flow. I noticed that none of the new properties were >> migrated over. Any thoughts on how to fix this besides just manually adding >> the changes? This feels like a bug in the parameter change management. >> >> Thanks, >> >> Mike >> >
