Hello,
If you can use the latest 1.10.0 release there is a new feature called
parameters that will greatly help with this.
You can use a new syntax #{my.secret} which will remain in the flow
when saved to registry.
Then you can use CLI commands for setting the value of the parameter
named "my.secret".
Thanks,
Bryan
On Thu, Nov 21, 2019 at 2:04 PM Bahlul Haider <bahlulhai...@gmail.com> wrote:
>
> Hello,
>
> I am working on automatically starting a flow from registry in newly
> created nfi clusters. To start the flow, I need to provide some secret
> values to some of the processors. What is the recommended way of
> programmatically provide secret of a processor?
>
> So far, I have tried NiFi CLI to pass secrets as variables to NiFi (e.g.,
> {secretName, secretValue}) and reference ${secretName} in the processor (I
> am aware that NiFi does yet support encryption for secrets in variables).
> However, I am unable to create a new version of the flow (from the browser)
> in the registry with ${secretName} as the property value (NiFi thinks it is
> a secret and does not include it in the new version). I was hoping that
> NiFi CLI have a way to update flow in registry with ${secretName} as secret
> value. However, I did not find a way to to do it.
>
> I am a newbie to nifi. Any help regarding this is greatly appreciated. I
> have seen there are several similar open issues in nifi. I am willing to
> work on those issues if my scenario is not supported.
>
> Thanks,
> Bahlul
