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

["ASF subversion and git services (Jira)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-11524:
--------------------------------------------------------

Commit 2049d5068b8238fc9251d3e735f1d80e0c86558b in nifi's branch refs/heads/main from Nandor Soma Abonyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=2049d5068b ]

NIFI-11524 Improved ExecuteStreamCommand documentation and configuration

This closes #7228

Signed-off-by: David Handermann <ex...@apache.org>


> 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: Extensions
>            Reporter: Nandor Soma Abonyi
>            Assignee: Nandor Soma Abonyi
>            Priority: Major
>             Fix For: 1.latest, 2.latest
>
>          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)