[NIFI-9894] Enhance InvokeHTTP process - Send content through body variable

• Type: Improvement
• Status: Open
• Priority: Trivial
• Resolution: Unresolved
• Affects Version/s: 1.15.3
• Component/s: Core Framework
• Assignee: Unassigned
• Reporter: Denis Jakupovic
• Created: 08/Apr/22 13:25
• Updated: 27/Mar/23 15:55

Description

Hey,

could you please implement an attribute in the InvokeHTTP processor where the processor sends a "body attribute" as raw content instead of the current content triggering an InvokeHTTP processor.

The process of sending JSON files through the processor currently is:
1. ReplaceText with content if needed

2. Call Invoke HTTP

3. Read Reponse variable or the new content created

3. ReplaceText with enriched content

Yes I know in Nifi 1.16 there is are two new processor for enrichment which needs then to be merged again. However, by working with a lot of RESTful services its quite a pain always to replace the content. The data lineage and provenance increases a lot as well.

imho better process in some use case:

1. InvokeHTTP with attibute as body
2. Read the "original" route instead of the response and read response adde attribute. (feature already available)

Issue Links

• duplicates: NIFI-6057 For InvokeHTTP processor, allow request body to come from an EL expression
• duplicates: NIFI-7596 InvokeHTTP - Get Request Body From Attribute
• relates to: NIFI-11331 InvokeHTTP: Add a property for the HTTP Body that can be marked sensitive