If we utilize an external zookeeper, it may be possible to maintain state across NiFi pod restarts.
Saving as a Template would maintain the processor ID, and initializing from a Template appears to let you set the value of a processor ID
We should look into creating a Template first during initialization, then deploying that template to the target NiFi instance.
it may prove valuable to update the flowlib data structure to be 1:1 compatible with this yaml structure so that we can deploy flowlib generated yaml to MiNiFi instances. Our data structure is already pretty close to this but has different field naming conventions
If we utilize an external zookeeper, it may be possible to maintain state across NiFi pod restarts. Saving as a Template would maintain the processor ID, and initializing from a Template appears to let you set the value of a processor ID
We should look into creating a Template first during initialization, then deploying that template to the target NiFi instance.
Also, MiNiFi contains a yaml export too for converting a template to a yaml file https://nifi.apache.org/minifi/minifi-toolkit.html#getting-started