[
https://issues.apache.org/jira/browse/NIFI-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy LoPresto updated NIFI-2974:
--------------------------------
Description:
A nice feature would be to allow per-user or per-instance configuration values
that could override default values for components (processors, controller
services, reporting tasks).
For example, in every {{GenerateFlowFile}} processor I add to a flow, I
generally want to change the *Run Schedule* from {{0 secs}} to {{1 sec}} to
stop from flooding the flow. In every {{LogAttribute}}, I want to log the
payload, so I change that value to {{true}}. As this issue originally stated,
an {{SSLStandardContextService}} often needs to be created with the default
keystore/truststore paths or with the
{{/Library/Java/JavaVirtualMachines/jdk<version>.jdk/Contents/Home/jre/lib/security/cacerts}}
path.
However, I do not believe these values are standard across the install base of
the application, so I cannot change them in the source code to impact all
users. I think being able to populate the Variable Registry with these values
using the FQDN of the component class and property would be an important
feature.
Example variable registry file (side note -- another good reason to enforce
property descriptors having a {{.name()}} without spaces and a human-formatted
{{.displayName()}}):
{code}
org.apache.nifi.processors.standard.LogAttribute.Log\u0020Payload=true
org.apache.nifi.processors.standard.GenerateFlowFile.generate-ff-custom-text=This
is a plaintext message.
...
{code}
was:
When users create a {{SSLContextService}}, some common default values could be
auto-populated:
* {{Keystore location}} - {{$NIFI_HOME/conf/keystore.jks}}
* {{Keystore Type}} - {{JKS}}
* {{Truststore location}} - {{$NIFI_HOME/conf/truststore.jks}}
* {{Truststore Type}} - {{JKS}}
These are the default values when using the TLS Toolkit and safe defaults for
manual generation as well.
> Allow for per-instance configuration values to override defaults for
> component properties
> -----------------------------------------------------------------------------------------
>
> Key: NIFI-2974
> URL: https://issues.apache.org/jira/browse/NIFI-2974
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.0.0
> Reporter: Andy LoPresto
> Labels: beginner, tls, ui
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> A nice feature would be to allow per-user or per-instance configuration
> values that could override default values for components (processors,
> controller services, reporting tasks).
> For example, in every {{GenerateFlowFile}} processor I add to a flow, I
> generally want to change the *Run Schedule* from {{0 secs}} to {{1 sec}} to
> stop from flooding the flow. In every {{LogAttribute}}, I want to log the
> payload, so I change that value to {{true}}. As this issue originally stated,
> an {{SSLStandardContextService}} often needs to be created with the default
> keystore/truststore paths or with the
> {{/Library/Java/JavaVirtualMachines/jdk<version>.jdk/Contents/Home/jre/lib/security/cacerts}}
> path.
> However, I do not believe these values are standard across the install base
> of the application, so I cannot change them in the source code to impact all
> users. I think being able to populate the Variable Registry with these values
> using the FQDN of the component class and property would be an important
> feature.
> Example variable registry file (side note -- another good reason to enforce
> property descriptors having a {{.name()}} without spaces and a
> human-formatted {{.displayName()}}):
> {code}
> org.apache.nifi.processors.standard.LogAttribute.Log\u0020Payload=true
> org.apache.nifi.processors.standard.GenerateFlowFile.generate-ff-custom-text=This
> is a plaintext message.
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
