[jira] [Commented] (NIFI-6077) Expression Language Force - give users decide where to use EL

["Rabits (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-6077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16782921#comment-16782921 ] 

Rabits commented on NIFI-6077:
------------------------------

Ok, I spent ~3d to prepare a small PoC for NiFi, it introduces forceEl field in the PropertyDescriptor and allows users to control - use NiFi Expression Language or not for the fields, that's not supporting the NFEL. Features:
 * User controlled force enable/disable Expression Language for any Property field (Processor / ContextService tested on ListenHTTP w/wo SSL
 * Interfaces for serialization/deserialization for templates / flow.xml.gz (hopefully it works with nifi-registry & cluster at all - need some time to test)
 * Sensitive properties affected too - so you can set the password in variable and use this value in sensitive property.

Hopefully successors will find a better way to implement the users needs and this PoC will help them to find a solution.

> Expression Language Force - give users decide where to use EL
> -------------------------------------------------------------
>
>                 Key: NIFI-6077
>                 URL: https://issues.apache.org/jira/browse/NIFI-6077
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Configuration, Core Framework, Core UI, Variable Registry
>    Affects Versions: 1.9.0
>            Reporter: Rabits
>            Priority: Major
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> For some reason right now extensions decide where to use and where don't NFEL - that's bummer. It makes complete automation impossible and DevOps unhappy.
> I think it will be good to twist this not a good practice and give users more freedom in using Expression Language / Variables whenever they want! And I think it could be solved by introducing forceEl flag for PropertyDescriptor, that could be set by user and saved with property value.
> With the change we can deprecate the old complex and non-intuitive setting support of EL in the extensions and even set forceEl by default for some extensions that already supporting EL scopes.
>  
> I'm already working on the first implementation here: https://github.com/apache/nifi/pull/3332



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)