Because we can deploy multiple flows to the same instance, it would be useful to provide global configurations and overrides in a file that can be committed to git. This will reduce the number of CLI arguments that are required when deploying a flow. For example, a flowlib.cfg might specify the nifi endpoint and component dir defaults so that they are not required cli args for every command. Those values could still be overridden by specifying the cli flags.
It could also be used for specifying reportingControllers and metricsReportingTasks which are not specific to a single flow deployment but need to be provisioned and enabled once per NiFi endpoint
Because we can deploy multiple flows to the same instance, it would be useful to provide global configurations and overrides in a file that can be committed to git. This will reduce the number of CLI arguments that are required when deploying a flow. For example, a
flowlib.cfgmight specify the nifi endpoint and component dir defaults so that they are not required cli args for every command. Those values could still be overridden by specifying the cli flags.It could also be used for specifying
reportingControllersandmetricsReportingTaskswhich are not specific to a single flow deployment but need to be provisioned and enabled once per NiFi endpoint