Jan-Henrik Preuss created NIFI-5707:
---------------------------------------
Summary: Ability to supply property values during transformation
in MiNiFi toolkit
Key: NIFI-5707
URL: https://issues.apache.org/jira/browse/NIFI-5707
Project: Apache NiFi
Issue Type: New Feature
Components: Tools and Build
Affects Versions: 1.7.0
Environment: NiFi 1.7.0
minifi-toolkit-0.5.0
Reporter: Jan-Henrik Preuss
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>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
