Details
-
New Feature
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
1.7.0
-
None
-
None
-
NiFi 1.7.0
minifi-toolkit-0.5.0
Description
Hello all,
in my NiFi flow I am using attributes that I define in an external property file.
I define this external file in the nifi.properties file by specifying the path.
Example:
nifi.variable.registry.properties=./conf/eadm-minifi.properties
Everything works fine so far.
I want to run this flow in MiNiFi. So I save my flow as a template and transform the template
with the minifi-toolkit-0.5.0 into a config.yml.
The saved template doesn’t contain information about the nifi.variable.registry.properties setting.
From my point of view, this is correct, since a template should not have system dependencies.
In consequence, the transformed config.yml won't have any property value from the original flow.
The resulting yaml file will for example look like this:
Core Properties:
variable registry properties: ''
So, currently I will always have to post process the created MiNiFi config.yml file
and edit "variable registry properties" key somehow.
I would like to have an option where I can define some values to use during the in minifi-toolkit-0.5.0 transform call.
For example:
java org.apache.nifi.minifi.toolkit.configuration.ConfigMain transform –D"variable registry properties"="./conf/eadm-minifi.properties" <input file> <output-file>