You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/06/29 20:54:00 UTC

[jira] [Commented] (NIFI-10162) Improve InvokeHTTP Property Configuration

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

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

Commit 7a47c8cfbd458ab037275762c385d50372c130a3 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7a47c8cfbd ]

NIFI-10162 Reorganized InvokeHTTP Properties

- Corrected handling of documentation for allowable values

NIFI-10162 Updated Multipart Form-Data Name description

This closes #6163.

Signed-off-by: Kevin Doran <kd...@apache.org>


> Improve InvokeHTTP Property Configuration
> -----------------------------------------
>
>                 Key: NIFI-10162
>                 URL: https://issues.apache.org/jira/browse/NIFI-10162
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The {{InvokeHTTP}} Processor includes a number of required and optional properties that support a variety of use cases. The introduction of framework support for dependent properties provides the opportunity to streamline the number of properties visible in the default configuration. Among others, properties related to proxy configuration and authentication can have dependencies applied to indicate optional status. Adjusting property ordering to place required properties first would also make the configuration easier to follow.



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