Good morning,
I love the introduction of parameters. They satisfy a longstanding need for
managing multiple sensitive values from a single spot. However, the
implementation does not satisfy the same functionality as variables. Based on
the comment inside NiFi stating that parameters are replacing variables, this
has me worried that I'm going to lose significant functionality if variables
stop being supported. Specifically, I use variables to assign non-sensitive
values throughout a NiFi in a way that can be transferred via templates. This
allows me to create a generic template, deploy that template, and configure the
specifics by just setting a few variables. It has sped up deployment
immensely. Parameters don't transfer with templates, and have to be added to
every processing group. I don't know of a way to have all processing groups
set to a parameter context all at once, so I would end up needing to create the
parameter context, add all the values, then add that parameter context to
dozens of processing groups. This would be a major step backward in
streamlining deployments.
Question 1) is NiFi planning to abandon support for variables?
Question 2) is there a way to address the issues I have with parameter
contexts? - inability to assign a parameter context to ALL processing
groups, or even all sub-processing groups under a selected processing group
- inability to transfer parameter context to new NiFi instances
Fred Pletz
