[
https://issues.apache.org/jira/browse/NIFI-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15626232#comment-15626232
]
Andy LoPresto commented on NIFI-2974:
-------------------------------------
I think what this may really come down to is a desire to have custom defaults
for processors on a specific installation -- for example, the above values, or
the fact that I often drop {{GenerateFlowfile}} processors onto a flow to test,
and would prefer that the default run schedule is {{3 sec}} rather than {{0
sec}}, the size was {{0 B}}, and the format was {{Text}} rather than
{{Binary}}. Similarly, with {{ReplaceText}} or {{LogAttribute}}, I have default
settings I prefer. It seems like overkill to make templates for each of those,
and I would forget to use them over the raw components or have to re-import
those templates every time I deploy a new instance. Perhaps with Variable
Registry, there will be a way to provide a custom definition file and have
components read from that file to populate their default values.
> Populate default values in SSLContextService creation dialog
> ------------------------------------------------------------
>
> Key: NIFI-2974
> URL: https://issues.apache.org/jira/browse/NIFI-2974
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Affects Versions: 1.0.0
> Reporter: Andy LoPresto
> Priority: Trivial
> Labels: beginner, tls, ui
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
