I think it might be simpler to implement it as a separate PackageContent processor that you would use right before InvokeHttp. Only because InvokeHttp is already quite complex, and really the packaging is a separate function from the http interaction.
PackageContent would be the reverse of UnpackContent. On Thu, May 16, 2019 at 11:26 AM Michael Di Domenico <mdidomeni...@gmail.com> wrote: > > On Thu, May 16, 2019 at 11:20 AM Bryan Bende <bbe...@gmail.com> wrote: > > > > Well MergeContent in general is meant to take many flow files and > > merge them together, so typically if you were using the flow file > > format, the idea would be to create a single flow file where the > > content contained (flow1 attrs, content)(flow 2 attrs, content) etc, > > but what I was suggesting was to try to configure the processor in a > > way that it never actually merges multiple flow files and just acts on > > 1 flow file. Essentially trying to use the packaging functionality of > > MergeContent without the merging, since there is no corresponding > > PackageContent processor to go with the UnpackContent processor. > > Oh, i see. I'll give it a try and see. > > Do you know how hard it would be to get the "Send flow" added into invokehttp?
