[
https://issues.apache.org/jira/browse/NIFI-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338298#comment-15338298
]
ASF GitHub Bot commented on NIFI-1974:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/501
@YolandaMDavis All looks good with the exception of needed to trim() the
filenames and one other thing that i noticed, which is that if multiple
properties files are specified and one cannot be loaded, none are loaded. I
will create an additional commit just to log this accurately and trim the
filename and push this to 0.x. I created a JIRA
https://issues.apache.org/jira/browse/NIFI-2057 to address the multiple files
better, but I don't want that to hold up the 0.7.0 release or prevent this from
making it into 0.7.0. I will merge this as-is with that minor change noted to
0.x.
> Support Custom Properties in Expression Language
> ------------------------------------------------
>
> Key: NIFI-1974
> URL: https://issues.apache.org/jira/browse/NIFI-1974
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Yolanda M. Davis
> Assignee: Yolanda M. Davis
> Fix For: 1.0.0, 0.7.0
>
>
> Add a property in "nifi.properties" config file to allows users to specify a
> list of custom properties files (containing data such as environmental
> specific values, or sensitive values, etc.). The key/value pairs should be
> loaded upon NIFI startup and availbale to processors for use in expression
> languages.
> Optimally this will lay the groundwork for a UI driven Variable Registry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
