When expression language is not supported by a field, it won't accept any
variables.
Mike
On Mon, Feb 18, 2019 at 10:34 PM Beutel, Maximilian <
maximilian.beu...@credit-suisse.com> wrote:
> Hello!
>
>
>
> Also asked the question on IRC, but figured the mailing list might be
> better for this longer question.
>
>
>
> For an InvokeHTTP processor I defined a SSL Context Service. In the SSL
> Context Service, in Keystore Filename property, I’d like to use a variable
> which I defined in a nifi.registry file. So in my nifi.properties I have:
>
>
>
> nifi.variable.registry.properties=./conf/custom.properties
>
>
>
> And in the conf/custom.properties I have:
>
>
>
> nifi.system.properties.file=C:/Users/some.file
>
>
>
> And in the field Keystore Filename in the SSL Context Service I input:
>
>
>
> ${nifi.system.properties.file}
>
>
>
> But then saving the SSL Context Service doesn’t work anymore, the
> validation fails and says “${nifi.system.properties.file} does not exist”.
> The actual file does exist however, but I suspect that the variable doesn’t
> get interpolated.
>
>
>
> According to
> https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-ssl-context-service-nar/1.5.0/org.apache.nifi.ssl.StandardSSLContextService/index.html
> it seems like expression language is not supported for Keystore Filename
> property. Does this also imply that variables won’t work in that field?
>
>
>
> Thanks for your help!
>
>
>
> Max
>
>
>
>
>
> ==============================================================================
> Please access the attached hyperlink for an important electronic
> communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
>
> ==============================================================================
>
