[
https://issues.apache.org/jira/browse/NIFI-13437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859791#comment-17859791
]
Joe Witt commented on NIFI-13437:
---------------------------------
My concerns around lack of a security context aren't important specific to this
proposed JIRA and are not a factor for consideration of this JIRA. I think we
need to do more work there but it is a separate issue.
Going back to the original response we need more context to evaluate what this
would be for to justify the deployment factors, user considerations and
potential code maintenance. Given how much energy has gone into getting rid of
extraneous code this has potential to be a step backward. While it would use
the parameter provider API and not the now removed variable registry mechanism
it does have the same fundamental weakness which is how is a given properties
file made available to the nifi instance in the first place. We've moved well
beyond that limitation through the examples of existing parameter providers
that as David points out large come from a central service. Same is true even
of the file one largely targeting a k8s deployment model.
Notably we already have a property based parameter provider
(PropertiesParameterProvider) in the code hierarchy - it is within the system
test hierarchy/for system testing.
Please help us understand the intent - not what it does (that part is clear)
but the why and how it would be used in a full deployment context.
Thanks
> Properties Parameter Provider
> -----------------------------
>
> Key: NIFI-13437
> URL: https://issues.apache.org/jira/browse/NIFI-13437
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Jim Steinebrey
> Assignee: Jim Steinebrey
> Priority: Major
>
> Create a Parameter Provider that can take as input a .properties file and
> create parameters for the property lines in the file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
