Hi William,
Wait/Notify may be a possible approach.
- UpdateAttribute
--> ReplaceText --> InvokeHttp --> Notify
--> Wait --> PutFile
- Use UpdateAttribute to add an attribute named 'wait.id' via
expression '${UUID()}'
- Connect the 'success' relationship from UpdateAttribute to both
ReplaceText and Wait processor, this clones the FlowFile, each
FlowFile has the same 'wait.id' attribute
- When InvokeHttp succeeds, Notify will release Wait processor
- If InvokeHttp fails, Wait will timeout
Hope this helps,
Koji
On Tue, Aug 27, 2019 at 6:56 AM William Gosse
<[email protected]> wrote:
>
> I have a situation where I need to do a post using an invokehttp for
> performing a lock operation on another web server. This requires me to do a
> replacetext in order to add the required json needed for the post. I wanted
> to do this call before I performed a putfile call on my system but that blows
> away the file content I needed to put. I really want to do these to calls in
> this order so if the invokehttp to get the lock fails I won’t do my put. I
> did try using the a mergecontent before the put in order the merge the
> original file content with the invokehttp calls content and that seem to work
> with some other gymnastics. I am looking for a better if one exists.
