You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Andrew M. Lim (Jira)" <ji...@apache.org> on 2023/06/08 21:37:00 UTC

[jira] [Updated] (NIFI-11524) Documentation and config experience improvement for ExecuteStreamCommand

     [ https://issues.apache.org/jira/browse/NIFI-11524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew M. Lim updated NIFI-11524:
---------------------------------
    Component/s: Documentation & Website

> Documentation and config experience improvement for ExecuteStreamCommand
> ------------------------------------------------------------------------
>
>                 Key: NIFI-11524
>                 URL: https://issues.apache.org/jira/browse/NIFI-11524
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Documentation &amp; Website, Extensions
>            Reporter: Nandor Soma Abonyi
>            Assignee: Nandor Soma Abonyi
>            Priority: Major
>             Fix For: 2.0.0, 1.22.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> This PR indends to add documentation for the ExecuteSteamCommand processor and improves the configuration experience by adding dependency between properties.
> I've noticed that the processor adds every Dynamic Property as environment variable even when it is a command argument. I didn't change this behavior because it might introduce a breaking change, but I'd change this behavior in a separate 2.0 only PR. Simply adding another regex check there would introduce the 4. regex check which is quite ugly so it would be a good opportunity for refactor. Another option would be to add validation for environment variables to ensure they don't contain {{{}.{}}}character, because most shells don't support it. But I'm not sure about that because there are commands that can utilize such env variables even though they are not common.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)